I’m so happy. I can think about what actually matters and tackle hard problems that were otherwise bottle-necked by how fast I could type syntax correctly on the keyboard.
the question conflates two things worth separating: enjoyment of problem-solving versus satisfaction of shipping.if most of your craft satisfaction came from debugging a subtle race condition or working out an elegant abstraction, that aha moment is harder to get when the agent gets there first. that's a real loss and worth naming honestly rather than hand-waving away.but if your satisfaction came from seeing something working, from momentum, from having built something a user can actually touch - agents compress the gap between idea and working software in a way that's hard to argue with.where it gets uncomfortable: watching the agent do the intellectually interesting parts while you review and manage QA. that discomfort is useful signal though. it means you were getting satisfaction from implementation work that, in hindsight, could have been delegated. the natural response is to move upstream - to the parts that still require judgment: what to build at all, which edge cases actually matter to real users, what the right abstraction is.for me as a solo founder it's been net positive. the craft satisfaction shifted, it didn't disappear.
I would offload boring stuffs like HTML, CSS to AI agent.
Core problem solving would start from prompting my brain.
I have been in programming for decade now, building my startup now.
AI as boring co-pilot, I would anyday feel happy.
Agents speed things up, but they also take away some of the small aha moments you get while figuring things out yourself. I think it depends on whether you enjoy the process or just the outcome.
As an older programmer, I’m actually happier using AI to write code. We already know what good engineering looks like, and now we’ve got a new toy we can learn from and have fun with.
I’m so happy. I can think about what actually matters and tackle hard problems that were otherwise bottle-necked by how fast I could type syntax correctly on the keyboard.
the question conflates two things worth separating: enjoyment of problem-solving versus satisfaction of shipping.if most of your craft satisfaction came from debugging a subtle race condition or working out an elegant abstraction, that aha moment is harder to get when the agent gets there first. that's a real loss and worth naming honestly rather than hand-waving away.but if your satisfaction came from seeing something working, from momentum, from having built something a user can actually touch - agents compress the gap between idea and working software in a way that's hard to argue with.where it gets uncomfortable: watching the agent do the intellectually interesting parts while you review and manage QA. that discomfort is useful signal though. it means you were getting satisfaction from implementation work that, in hindsight, could have been delegated. the natural response is to move upstream - to the parts that still require judgment: what to build at all, which edge cases actually matter to real users, what the right abstraction is.for me as a solo founder it's been net positive. the craft satisfaction shifted, it didn't disappear.
I would offload boring stuffs like HTML, CSS to AI agent. Core problem solving would start from prompting my brain. I have been in programming for decade now, building my startup now. AI as boring co-pilot, I would anyday feel happy.
Agents speed things up, but they also take away some of the small aha moments you get while figuring things out yourself. I think it depends on whether you enjoy the process or just the outcome.
As a hobbyist and indie hacker, love it. As a professional maintainer - it made a dry job dryer, faster.
As an older programmer, I’m actually happier using AI to write code. We already know what good engineering looks like, and now we’ve got a new toy we can learn from and have fun with.
No