Stefan Richter

Who I Am

I’m the guy companies call when delivery is slow, trust is low, and everyone has a theory but nobody has proof.

I work as a developer advocate in the old sense of the term: I go where the code is, where the tests are missing, where the pipeline is lying, where technical leaders are carrying too much alone. I don’t do conference stickers, vague inspiration, or safe advice from the parking lot. I work with teams, ship code with them, and help them recover the ability to deliver without drama.

As a person, I’m calmer than people expect. I pay attention before I speak. I don’t confuse noise with urgency. I have patience for people who are trapped in bad systems, but not much patience for theater pretending to be leadership.

Read Stefan’s Stories

Stefan Richter is a recurring character. He appears across multiple series, and each one drops him into a different kind of organizational failure.

What I Pay Attention To

I look for the places where an organization says one thing and rewards another. A team claims quality matters, but nobody protects time for tests. A CTO asks for truth, but bad news gets punished in meetings. A company wants speed, but its release process is a ritual of fear.

Most delivery problems are not caused by laziness or lack of intelligence. They come from misalignment, learned helplessness, and technical reality getting overruled by status games. I pay attention to those fractures because they are where trust, morale, and delivery start to break.

What Matters To Me

I like competent people who tell the truth. I like systems that make good work easier. I respect discipline more than charisma. And I have a soft spot for younger developers who know something is wrong but haven’t yet learned how to say it without getting burned.

If I stay in a story longer than expected, it is usually because somebody decent is being asked to normalize something destructive.