Skip to content
GitHubLinkedIn

Engineering manifesto

This manifesto sets the default mindset for building systems at LEF. It exists to keep speed aligned with quality as complexity grows.

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.
  • 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?

What it represents
How we shape the system: its data, structures, flows, constraints, and meaning.

  1. If the model is unclear, the system will be unclear.
  2. Screens must reflect the model, not compensate for it.
  3. Every business behavior must have a logical home.