Very well said Ryan, fully agree.
Still wonder about posts of people using agents to churn out 15kLOC per day, which always makes me think "that's not a good thing" and "what are you doing with so much code?!".
A fundamental division between schools of thought in programming is (a) the elimination through simplifying of cruft, boilerplate, and extra abstraction layers, and (b) the automation of maintaining cruft, boilerplate, and extra abstraction layers.
One of the reasons I drifted away from C and newer languages with adjacent philosophies towards a subset of C is that I found myself in the first camp. Some problems were simply not as hard as I was making them. Memory management, threading, UI, and so on could be simplified such that not only the high level C code became simple, but the actual machine code also became simple.
This is starkly different from modern C and Rust programming culture, where the philosophy is simply that dealing with the complicated lower level details is a matter of *automation*. The compiler needs to generate something extra, it needs to check extra things, and so on.
âAgentic programmingâ falls into the latter camp, and this is also why I donât employ it in my workflow (other than search engine usage and so on). I donât need it to generate 10s of 1000s of lines of code. The requirement of 10s of 1000s of lines of codeâfor implementing something derived from the information content inside a tiny promptâis an architectural red flag.
Perhaps a substantial portion of that code simply shouldnât exist. I find that my programs become much better when I do that simplification pass first. After that, thereâs drastically less boilerplate, less maintenance, and less busywork to begin with.