Jason Fried says he can build and design software solo again
DHH replied with four words, and neither of them showed a number or a shipped result.
Jason Fried posted a timeline of his own career and ended it with a claim worth sitting with. Thirty five years ago he wrote, built, sold and released software solo. Twenty five years ago he still did all the design himself, sketches, then HTML, then CSS. Fifteen years ago he was mostly directing others to implement his vision. Five years ago he was primarily directing, and, in his words, his "I can do it myself" muscles had atrophied.
Today, he says, he is back to the beginning, able to write and design software entirely by himself. He adds that having an elite team of others who can each do the same is an enormous multiplier. DHH amplified the post with one line, "The plan was there all along."
My "I can do it myself" muscles had atrophied.
Able to write and design software entirely by myself. And having an elite team of others who can do the same thing is an enormous multipler.
What is actually new here
Solo founders shipping alone is not news, and it is not what Fried is describing. He is describing the reverse trip. Someone who spent a decade and a half moving away from the keyboard, into direction and review, has gone back to doing the work personally. That is a different claim, and it points at a different question for anyone hiring.
If senior people who stopped building can pick the work back up, the shape of a team changes. You are not staffing a hierarchy where one person holds the vision and several people implement it. You are staffing a group of people who can each carry something end to end, which is exactly the multiplier Fried names.
The honest caveat is that this is a feeling, not a result. Neither Fried nor DHH posted a number, a product, a timeline or a shipped thing attached to the claim. No before and after, no hours saved, no output. It is one very experienced builder describing what his hands can do again, and one very experienced builder agreeing.
Our read is that the useful part is the framing, not the proof. Advances that give back a capability you lost are harder to notice than advances that give you something new, and they change the org chart quietly.