3 ms·

> This is the sentiment being hyped up around the industry currently: traditional coding is all but dead, and Spec Driven Development (SDD) is the future. You g

> This is the sentiment being hyped up around the industry currently: traditional coding is all but dead, and Spec Driven Development (SDD) is the future. You generate a plan, and disconnect from writing any code Agentic agile > agentic waterfall (at least for now) Don't give the AI a spec, work with it every step of the way. > pulls the slot machine lever over and over (link to "One More Prompt: The Dopamine Trap of Agentic Coding") I'm sure the first cave-person to discover how to make fire was equally "addicted" to making fires. That doesn't really say anything about the underlying technology. > An increase in the complexity of the surrounding systems to mitigate the increased ambiguity of AI's non-determinism I don't know what this means, exactly. Anyone have any ideas? > Atrophying skills for a wide swath of the population This is very real and something we're going to have to contend with. Software can't really become less complex, and there's a minimum amount of knowledge you need, with or without AIs there to help you. We may need specialized training academies for developers where they spend a few years without AI to learn to program, and then are given a few years of AI programming. > Vendor lock-in for individuals and entire teams This isn't really a big program, you can always switch AI providers if there's frequent downtime. > only a skilled developer who's thinking critically, and comfortable operating at the architectural level, can spot issues in the thousands of lines of generated code, before they become a problem Agreed... > Yet, in an ironic twist of fate, it's the individual's critical thinking skills and cognitive clarity that AI tooling has now been proven to impact negatively. ...well, yes and no. AI tooling can help you _reduce_ cognitive debt. Picture this: There is one senior developer (Person A) on the team who understands Service X. Your other developers could schedule time with Person A to get an understanding. Or, they could ask the AI to analyze the project and explain it to them. This scales much better, and if Person A is a poor communicator (let's face it, many senior engineers are), it might be the only working option.

larsfaye 6mo ago
Author here.... "An increase in the complexity of the surrounding systems to mitigate the increased ambiguity of AI's non-determinism" I'm referring to the layers of review that are needed to be put in place to reign in the fact that the code that is generated is blurry and obfuscated, and in amounts that exceed what someone can review in one or two sittings. I'm seeing multi-phase AI review stages that will try and distill review finer each time. Then another agent layer to document. Then another to create a PR. Then the human reviews, but uses Coderabbit locally. Then sends it back into the pipeline and round and round we go, all because there's simply too much volume of code to review.

larsfaye 6mo ago

Author here.... "An increase in the complexity of the surrounding systems to mitigate the increased ambiguity of AI's non-determinism" I'm referring to the layers of review that are needed to be put in place to reign in the fact that the code that is generated is blurry and obfuscated, and in amounts that exceed what someone can review in one or two sittings. I'm seeing multi-phase AI review stages that will try and distill review finer each time. Then another agent layer to document. Then another to create a PR. Then the human reviews, but uses Coderabbit locally. Then sends it back into the pipeline and round and round we go, all because there's simply too much volume of code to review.