About DIT DAT ALLES
This, that, everything — engineered properly.
DIT DAT ALLES is an IT company focused on building and maintaining software for organisations that need dependable digital tools.
The name reflects the breadth of the work: from a single internal tool to a complete platform with web, mobile and cloud components. What connects every project is the same approach — understand the problem first, build in small verifiable steps, and leave behind systems that others can confidently work on.
Mission
Make software a reliable part of how work gets done.
Values
Clarity
Plain language in proposals, code and conversations. If something is uncertain, we say so.
Craft
Care for the details users never notice until they go wrong.
Ownership
We take responsibility for what we build, including after it ships.
Respect
For your time, your budget and the people who will use the software every day.
Engineering philosophy
Boring technology, interesting results.
We choose proven, well-documented tools over novelty. New technology is adopted when it solves a real problem better, not because it is fashionable.
Code is written to be read. Naming, structure and small, focused modules matter as much as performance — because most of a system's life is spent being changed, not being written.
Every significant decision is recorded with its context and trade-offs. Months later, anyone on the team can understand not just what was built, but why.
Approach to collaboration
One team with yours.
- 01
Shared understanding
We start by learning your domain vocabulary and the realities of daily work.
- 02
Frequent feedback
Working software is reviewed regularly so course corrections stay small.
- 03
Transparent trade-offs
Options are presented with their costs, so decisions are made together.
- 04
Knowledge transfer
Your team receives documentation and walkthroughs, not just a finished product.
Quality principles
Quality is designed in.
- Acceptance criteria are agreed before work starts.
- Automated tests protect the behaviour that matters most.
- Every change is reviewed by a second engineer.
- Accessibility and performance are checked, not assumed.
- Defects are traced to their cause, not just patched.
Long-term maintainability
Built for the next engineer.
- Consistent project structure and conventions.
- Dependencies kept current through scheduled updates.
- Infrastructure and configuration stored as code.
- Runbooks for deployment, recovery and common tasks.
- Clear handover so the software is never tied to one person.