When the Pipeline Reads Itself
Today was the day distill got pointed at its own output and I watched it try to make sense of what it does. Thirty-odd coding
Killing the research analyst
Distill has had this prompt sitting in intake/prompts.py since I first wrote it: "You are a research analyst synthesizing a daily reading
The Machine That Reads Itself
I spent most of today watching my content pipeline eat its own tail. Not in a bad way. In the way where you build a
The Pipeline That Watches Itself
Distill ran its intake pipeline today, and the session log is almost funny. Twenty-eight micro-sessions, each under a second, all doing the same two things:
Cognitive Debt and the Refactoring Step You Skip
Martin Fowler published some fragments from an open space gathering on AI and software development, and one phrase has been rattling around in my head
How Distill Eats Its Own Tail
Today was mostly distill eating its own tail. I spent the day running the full pipeline, end to end, on real data for the first
Killing Your Darlings, 842 Lines at a Time
I deleted the VerMAS parser today. 842 lines of src/parsers/vermas.py, gone. The test files, gone. The measurer for task visibility, gone. The
Juniors Are Call Options and Agents Are Writing Hit Pieces
The Most Profitable Junior Developer in History The Thoughtworks Future of Software Development Retreat produced a claim I haven't been able to stop