Engineering Philosophy
Build. Think. Break. How we develop software and why we attack it ourselves in the end.
How we work
The 60/20/20 Philosophy
A mindset, not a split of working hours. It describes how we build: build fast, think critically, try to break our own solution.
BUILD60 %
Build what runs
We develop, integrate and deliver. A working prototype teaches us more than a long concept, and small steps beat the big bang.
THINK20 %
Question requirements
We ask what is really needed and what it means for operations, maintenance, security and extensibility. Sometimes the best solution is to build less.
- A simple list instead of batch tracking, as long as the simple solution is enough
- Protection inside our own module, because the external system only knows full access
BREAK20 %
Break our own solution
We look for failure cases, edge conditions, data deviations and security gaps before a customer does. Not every finished feature is automatically ready for operations.
- Export compared document by document with the source system before it went live
- Vending machine bookings compared with existing documents over 18 months
- Development and test environment as a neutralised clone of production
Code fast. Think critically. Hack mercilessly.Human-directed. AI-powered. Adversarially tested.
This describes our way of working, not a certification. The case studies show which checks we actually carry out.
Artificial intelligence in our work
AI-assisted development tools are part of the way we work. They speed up development, analysis, documentation and review. People remain responsible for architecture, requirements and results.
We do not turn this into a sales pitch. What matters is what ends up at the finish line: a solution that works, that can be explained and that somebody maintains.
What we do not mean by this
- No literal split of project hours. 60/20/20 describes a mindset.
- No certification and no guarantee. Which checks we actually carry out in a project is described in the respective case studies.
- No claim that every feature is automatically ready for operations. Quality comes from critical questioning and systematic testing.
What would this look like for your project?
We are happy to explain how we would go about it.
Discuss a project