Case · Netherlands Ministry of Defence
Nick spent nearly twelve years as a software developer for the Ministry of Defence, on mission-critical systems in a strictly regulated setting. About the content we can say little. About the working attitude it produces, a great deal.
The context
At the Ministry of Defence, software supports work that people have to be able to rely on. Including at moments when there is no room for an outage.
Nick helped build it for nearly twelve years, as a software developer on mission-critical systems. A setting like that comes with strict rules on quality, security and control. Every change is tested before it goes live, and every choice has to be explainable.
What exactly he built there, we will not tell you. That falls under confidentiality, and rightly so. An organisation that handles its information carefully expects the same of the people who work for it. We take that attitude to every client, so to you as well.
The habits
Working that long in a setting like that changes how you build. It becomes second nature rather than procedure. Four habits Nick takes to every project.
Prove it works first, roll it out after. The reason is not a checklist, it is knowing what happens when it goes wrong.
Recording code and choices so a colleague can pick it up tomorrow. Knowledge that sits in one head only is a risk. In a small company too.
Security is a design question, not a layer you add afterwards. From the first sketch you think about who may see what, and what happens if someone tries to abuse it.
If something breaks, you do not guess or restart in a panic. You find the cause, restore in a controlled way, and make sure it does not happen again.
What this gives you
Your workspace holds your client data, your quotes and your invoices. The heart of your company. That deserves the same care as a system that is not allowed to fail.
Curious how we handle security and your data? We explain that in the FAQ.