20 years ago, in 2006, I had already found part of the answer.#
But what I had wasn't a system. Not yet.
The question, the one I'd started asking in 1998:
How does a developer actually improve?
In 1998 I was running my first serious projects in cooperation with other developers.
The question wasn't theoretical. It was every day.
The good ones around me weren't doing what training said they should do.
They were doing something else.
I wanted to know what.
By 2006 I had some answers.
I knew which habits mattered.
I knew which kinds of feedback made developers level up.
I knew which trainings actually moved the needle and which didn't.
What I didn't have yet was a SYSTEM.
A way to put the answers into a sequence someone else could walk.
Not just "this worked for me," but "this is reproducible, level by level."
That took another 20 years.
Three things I learned in the time between:
1. The question isn't "how do I get better?"
The question is "how do I know I've gotten better?"
Most developers can't answer the second one.
A system answers the second one.
2. Improvement isn't linear.
You'll feel stuck for months, then jump in a week.
The plateau IS the training, if there's a system catching you on the other side.
3. The teachers who matter aren't the loudest.
They're the ones who hold up a mirror and stay quiet,
inside a structure that lets the mirror mean something.
Almost 30 years in.
I'm still adding to the system.
What's the question YOU started asking?
And are you asking it inside a system, or still alone with it?
#SoftwareCraft
