Why do technical problems so often turn out to involve fatigue, fear, communication or faulty assumptions?
Programming, frustration, mental models, competence and the person sitting behind the keyboard.
The collection
A practical reflection tool for finding hidden assumptions, testing mental models against reality, and turning recurring friction into useful feedback.
The most dangerous software you will ever run is not on your laptop. It is the collection of assumptions, mental models and stories quietly governing your decisions before you ever notice they are there.
Why the developers who last are often the ones who can stay useful while confused, frustrated, bored and uncertain.
A personal reflection on why competence often begins with public embarrassment, social resistance, repetition, and the willingness to look like the village idiot before skill finally arrives.
Why software developers need to maintain more than their code.
Keep exploring
How can a vague career question become a route someone can actually follow?
What happens when the question is personal and refuses to fit anywhere else?
How did computing become what it is?
