Able to ≠ willing to
jasonleow • 14 Jan 2026 •
It’s crazy how good Claude Code is these days for coding. To the point it became a hype train.
“Everyone’s able to build software now!”, the influencers shout.
But able to doesn’t mean willing to.
Most people conflate the two.
The gap between ability and willingness is as wide as an ocean, to be honest. It’s like saying, just because the smartphone put a camera in everyone’s pocket and made photography ubiquitous, doesn’t suddenly make everyone a professional photographer, right? Nor are normies automatically interested to become one, just because an easy-to-use tool now exists.
And as far as I know, photographers still have a job. They simply moved up the value chain, to jobs and situations where a phone camera won’t cut it, where people are still willing to pay for a pro’s expertise, where the occasion is formal and important.
Your dev job is safe, bro.
Get back to work.
Comments
@Winkletter 100%. It’s often the case, a new revolutionary tech might lead to some loss of old jobs, but over longer term, it mostly leads to more new jobs being created
The camera phone is a great example. Another good one I’ve heard is the ATM. You would think banks wouldn’t need tellers anymore. But the ATM actually led to a doubling of teller jobs because banks could now afford building more banks. And the tellers were doing higher level work.