Recovering from pushing out an article on coroutines [1]; coordinating getting the house in order for the workweek [2]; and drafting a package to make literate programming in org-mode a bit more to my liking.
Part of what makes a classic a classic is that it survives a test of time. I'm not sure that Person of Interest is old enough yet to qualify, but it definitely seems to be on its way.
Pork tenderloin has been on my rotation about once a week lately! Delicious, lean, easy. I do it with asparagus and it seems fancy given the simplicity. Enjoy.
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.
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.
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., or 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.
--Richard Guindon
reply