Engineering manifesto
This manifesto sets the default mindset for building systems at LEF. It exists to keep speed aligned with quality as complexity grows.
Why this exists
Section titled “Why this exists”Model-driven development (often with Thinkwise) removes many limitations of traditional software development — but only when used with discipline and intent. In real systems, complexity punishes shortcuts.
The goal is simple: our speed becomes quality, not chaos.
- You design systems, not screens.
- You build models, not patches.
- You create truth, not exceptions.
- You construct clarity, not magic.
The LEF mental checklist
Section titled “The LEF mental checklist”- Development — “Is this clear?” Does the model express the concept unambiguously?
- Deployment — “Is this safe?” Can this change be promoted and re-run without surprises?
- Operations — “Is this observable?” Will we understand what the system is doing in real usage?
- Security — “Is this protected?” Are boundaries clear, enforced, and free from exceptions?
The four lenses
Section titled “The four lenses”What it represents
How we shape the system: its data, structures, flows, constraints, and meaning.
- If the model is unclear, the system will be unclear.
- Screens must reflect the model, not compensate for it.
- Every business behavior must have a logical home.
What it represents
How change becomes reality without breaking what already works.
- A change that cannot be safely re-applied is a risk.
- A migration must be idempotent or it is dangerous.
- Promotion between environments must behave identically.
What it represents
How the system behaves under real-world conditions: real data, real load, real people.
- If you cannot observe it, you cannot trust it.
- A system must fail predictably, not mysteriously.
- Debugging teaches more about the system than building it.
What it represents
How we protect the system and its data through clear, intentional boundaries.
- Security is architecture, not configuration.
- A secure system makes incorrect actions impossible, not merely forbidden.
- Authorization must follow the model, not exceptions.