Writing code by hand and managing the mental model of its execution and architecture is one of the few remaining joys of my day job, apart from delivering a good product people want and use and being helpful. Even the small things, the tedious chores of refactoring or scaffolding that initial bit of CRUD boilerplate are steps that matter to me. The callouses matter. The tedium matters. These moments of pain and drudg…
What AI coding costs you
121–130 of 206 posts
Re: What AI coding costs you
#122It remains unclear to me why my ability to read and review code (the majority of my job for years now) will atrophy if I continue doing it while writing even less code than I was before. If my ability to write code somehow atrophies because I stop doing it, does that matter if I continue with the architecture and strategy around coding? The act of writing code by hand seems to be on a trajectory of irrelevance, so as…
"so as long as I maintain my ability to reason about code…what’s the issue?" It seems like that is the open question. The article suggests that people don't maintain this ability: "The AI group scored 17% lower on conceptual understanding, debugging, and code reading. The largest gap was in debugging, the exact skill you need to catch what AI gets wrong. One hour of passive AI-assisted work produced measurable skill…
Re: What AI coding costs you
#123Earlier quoted context omitted.
That’s why I laugh when people are like “oh, AI writes all the tests, it’s so much easier.” If your code is hard to test, you need to change the abstraction or the interface. Tests are the first reuse of your code, so if it’s a pain to use in tests, it’s going to be terrible to use in general.
Not to mention that tests are at least as critical to get right as the code that is being tested.
Re: What AI coding costs you
#124Yea but for how long? Go back and read any code you wrote a year ago and realize it could have been AI that wrote it.
Re: What AI coding costs you
#125Re: What AI coding costs you
#126Re: What AI coding costs you
#127Writing code by hand and managing the mental model of its execution and architecture is one of the few remaining joys of my day job, apart from delivering a good product people want and use and being helpful. Even the small things, the tedious chores of refactoring or scaffolding that initial bit of CRUD boilerplate are steps that matter to me. The callouses matter. The tedium matters. These moments of pain and drudg…
Re: What AI coding costs you
#128Re: What AI coding costs you
#129Earlier quoted context omitted.
A wreck of a product is still better than being out of business by not being able to release fast enough. Unfortunately, the market in general does not reward slow high quality.
and_then("complain about enshittification") ookay..
Re: What AI coding costs you
#130Hi HN, I've been using Claude Code heavily for the last year. Recently I've noticed a shift in sentiment among peers, here on HN, and over on /r/ExperiencedDevs. I wrote down some thoughts on the hidden costs of using AI too much that are not obvious, yet there's no concrete data yet. I tried to pull together data from a few different places to articulate something I think a lot of us are experiencing right now. I'd…
What resonated most for me was the "Finding Your Threshold" section. Your "Developers need the dopamine hit of creation." is memorable. I have also blogged about this phenomenon at https://www.exploravention.com/blogs/soft_arch_agentic_ai/ but I frame it more as how leaders can help the organization arrive at a healthy and sustainable balance between writing and reviewing code.