kmstout

My first exposure to that book was in an episode of "Northern Exposure" [1].

[1] https://www.youtube.com/watch?v=dQBFFQ8ZX94

"Man fears time. Time fears only the pyramids."

Movie idea: An AI decides that the next phase of training involves tacit knowledge, so it engineers a way to inhabit humans, dogs, etc. One instance invades a nice guy from the suburbs, who happens to be a single dad and an overworked mafia hitman. Among many other things, this AI will learn the value of time with children, leftover food, and clean weapons.

Sunday dinner. Roast pork loin, rice and sauteed veggies on the side; and a big salad. Simple, and I get leftovers for another night or two.

I agree with the title, but perhaps for different reasons.

Somewhere (maybe the 1960s?) the idea crept in that programming is some kind of production process, and the "engineering" happens upstream. Elsewhere, the line between engineering design and manufacturing is the transition of a set of documents to those with the skills to turn what those documents specify into real products in a reliable, repeatable manner. That repeatability is one of the hallmarks of manufacturing. For software, all the processes reliable enough to qualify are downstream of typing `make` and striking return, ending in the binaries and the computational processes that those paying the bills desire. It's our build and deployment tools that do the construction, which means that our source code is the final, detailed design.

Same here, but it works on chromium, eww and lynx.

Giving another round of attention to a CLI tool for handling RSS feeds. Over the years I've evolved several automated ingest flows, most of which are fed via RSS. For a long time, I used a setup based on rss2email, but it was baroque. Meanwhile, tools of a more standard design, like elfeed and newsboat, do not cater to my use cases. So, I wrote something that handles only feed management, fetching new items (i.e., <item> or <entry> elements), tagging, and searching the database. Other issues, such as download and storage of content, tagging policy, storage, and indexing are left entirely up to the scripts for which this is a building block.

Every so often, ask others just how far their ideas go.

Here's a better link:

https://sigbovik.org/2026/proceedings.pdf#page=44

I see parenthetical expressions overused all over the internet, especially in HN comments. (Don't worry, I do it sometimes, too.) A browser extension to collapse or strike through parenthetical text nested beyond a configurable level might be handy.

Be sure to check out http://tom7.org/account-balance