an issue a lot of algorithms have is either not showing you enough of what you want, or pigeonholing you.

ColdFusion SOAP Web Service Suddenly Returning ‘Unable to Find Operation’

Your SOAP web service worked perfectly yesterday. Clients consumed it without errors. Today, every request returns “Unable to find operation.” You did not change the code. You did not restart the server. The service simply stopped responding.

Even after being pressured into providing an escape hatch, somehow they failed to add "the 24-hour wait can be skipped during initial setup on a new device." This reveals that none of the decision makers understand or care about our use-cases.

Music player in text editor (minimal TUI driving an `mpv`).

Cut/paste integration:

cutting one or more lines will remove a song from the playlist and put full path of song file in the clipboard (a partially selected line is cut in full);

pasting enqueues the clipboard contents, interpreted as one or more files, into playlist.

Undo integration.

Editor exposes undo as a tree, so I can always return to some prior playlist state.

Want to hear song I was playing yesterday, feeling lazy about doing narrowing/fuzzy search for name (<10 keystrokes, but mental load higher).

Hit undo until song appears.

Copy song.

Mash redo until changes stop.

My big heuristic for deciding whether some logic should be a method on a class or a standalone function that takes the class as a parameter, all else being equal:

Can we make it more modern?