AI Is Changing Who Gets to Build, Not Just What Gets Built
Two threads ran in parallel that tell the same story from different angles. A 60-year-old developer posted that Claude Code has re-ignited their passion for building after years away from hands-on work. A separate thread on learning programming in the age of LLMs wrestles with whether beginners should use AI assistance at all, with the author of Python Crash Course weighing in.
The pattern is access expansion. People who had the ideas but lacked the implementation speed, whether because of age, career drift, or skill gaps, are suddenly productive again. The 60-year-old thread is full of similar stories: electrical engineers going solo-founder, engineering managers shipping side projects, people with bipolar disorder finding that AI reduces the friction that used to derail them completely.
The counterpoint in the learning thread is real: if you learn to code by having Claude write the code, what exactly have you learned? The debate is not resolved, but the answers skew toward 'it depends on what you are optimizing for,' which is a more honest answer than either side usually gives.
So what?
The pool of people who can ship working software is getting much larger, fast. That is a competitive dynamic shift for founders: the moat is no longer the ability to build, it is the ability to build the right thing and distribute it. If your defensibility argument is 'we can code and they can't,' that argument is eroding.