What I think is also good about the piece is that it shows how using this tech eventually funnels people down a particular direction. This is captured also by this exchange on lobste.rs: https://lobst...
@nprofile1q... @nprofile1q...
Really good thread, and a really good blog post, or essay, I should say. I respect the honesty in it, and I understand the standpoint.
However, I want to share a genuinely different experience: using Claude Code and similar tools has actually made coding more enjoyable for me, not less. And I don’t think I’m in denial about that. I've learned a lot more over the past year through GenAI since ever before, and I've been coding for the web almost every day for nearly 30 years.
The difference might come down to how you approach it. If your relationship with the tool turns into just "tapping Y and hoping for the best", then yeah, that IS miserable. But that's not the only way to look at it.
For me, it feels more like having a really fast pair programming partner. I still make the architectural decisions, I still write specs, I still understand why things are the way they are, and I still review everything. And I still code, some. But I no longer need to power through the tedious parts, the boilerplate, the plumbing, the bits I've written hundreds of times. That frees me up to focus on what I actually enjoy: the design, the problem-solving, the features, the “what if we tried this” moments, the drafting, and the documentation.
The drinky bird pipeline is real, and it’s a valid concern but it’s not inevitable. It’s a choice. The tool doesn't make you check out, but it does make it easy to, and that’s something worth being honest about.
Where I completely agree: the systemic concerns don't go away just because individual use can be responsible. And the skill-atrophy risk is real for those still building their foundations. Not everyone is in the same position when picking up these tools.
#AI #GenAI #ClaudeCode
Really good thread, and a really good blog post, or essay, I should say. I respect the honesty in it, and I understand the standpoint.
However, I want to share a genuinely different experience: using Claude Code and similar tools has actually made coding more enjoyable for me, not less. And I don’t think I’m in denial about that. I've learned a lot more over the past year through GenAI since ever before, and I've been coding for the web almost every day for nearly 30 years.
The difference might come down to how you approach it. If your relationship with the tool turns into just "tapping Y and hoping for the best", then yeah, that IS miserable. But that's not the only way to look at it.
For me, it feels more like having a really fast pair programming partner. I still make the architectural decisions, I still write specs, I still understand why things are the way they are, and I still review everything. And I still code, some. But I no longer need to power through the tedious parts, the boilerplate, the plumbing, the bits I've written hundreds of times. That frees me up to focus on what I actually enjoy: the design, the problem-solving, the features, the “what if we tried this” moments, the drafting, and the documentation.
The drinky bird pipeline is real, and it’s a valid concern but it’s not inevitable. It’s a choice. The tool doesn't make you check out, but it does make it easy to, and that’s something worth being honest about.
Where I completely agree: the systemic concerns don't go away just because individual use can be responsible. And the skill-atrophy risk is real for those still building their foundations. Not everyone is in the same position when picking up these tools.
#AI #GenAI #ClaudeCode
1
