Who builds, answers

A sentence as a blueprint

“Who builds, answers.” On stoicera.com this is a building rule, not an advertising line. It shapes the work we accept, our contracts and why nobody stands between a client and the person writing the code.

Software has invented many ways to avoid answering: anonymous ticket queues, agency layers that disperse responsibility and staffing based on availability rather than accountability. We deliver work instead of lending staff, because it improves how we build, not because other models are immoral. Knowing you will get the call in three years changes how you build today.

Responsibility is concrete or it is absent

Responsibility is not abstract. It is a working phone number, a legal notice with an address, a project directory distinguishing finished and unstarted work, a stable price and an instance per municipality showing whose data live where.

That is why this website lists projects with status and stack, and labels planned work “in preparation”, not “ongoing”. A flattering register is just numbered advertising.

What teaching taught me

Teaching IT at BBRZ Vienna shows me the same principle from another side. In front of adult learners, jargon cannot hide whether the material works. You see it immediately in their faces. Teaching is software without deployment delay: feedback is real-time.

Having to explain what you build makes you build more clearly. I now consider this an underrated quality mechanism: could I explain this system to someone who trusts me and knows nothing about technology?

The foundation beneath the sentence

I rarely write about my faith because it is not a brand. Omitting it here would be dishonest: accountability is a conviction for me, not a business strategy. Work must stand before someone, not merely a quarterly report. The same principle can have Stoic, Christian or simply craft foundations: build as if you had to stay. Then stay.