Earlier quoted context omitted.
That's interesting. I have been thinking about how the vastly different reactions people seem to have to agentic coding could be influenced by what they value about coding. To me it seems like there are three joys in coding: 1. Creating something 2. Solving puzzles 3. Learning new things If you are primarily motivated by seeing a finished product of some sort, then I think agentic coding is transcendent. You can get…
I think I'd add a #4 to this list, and that's helping people. I like making things that people can use to make their life easier. That's probably my number one. The "creating something" idea... That's more complex. With agentic coding something can be created, but did I create it? Using agentic coding feels like hiring someone to do the work for me. For example, I just had all the windows in my house replaced. A crew…
The inherent value of creating is something I was missing. Solving puzzles might be part of that, but not all. It's the classic Platonic question about how we value actions: for their own sake, for their results, or for both.
I think we agree that coding can be both, and it sounds like you feel the value for its own sake is lackluster in agentic coding -- It's just too easy. And I think that's the core sliding scale: Do you value creation more for its own sake or for its results? Where you land on that spectrum probably influences how people feel about agentic coding.
That being said, I also think that agentic coding can give enough of a challenge to scratch the itch of intrinsic value of creating. To a certain degree I think it's about moving up the abstraction chain to work more on architecture and product design. Those things can be fun and rewarding too. But fundamentally it's a preference.