Skip to content

Knowledge base

Engineering Philosophy

Engineering philosophy is the reasoning beneath engineering rules: work flows best when a team can change its part of a system alone, sees the effect of its decisions fast, and keeps learning. People who have internalized that reasoning need fewer rules to act on it.

Written by

Updated:

Software Engineering 5

Our position. We hold that cheaper development makes engineering discipline more valuable, not less. When code generation is nearly free, the ability to write code is the wrong differentiator, and architectural discipline and context engineering become the moats (ten-dollar development (opens in a new tab)).

The Three Ways, from The Phoenix Project, describe how work should move through a delivery system. Fast flow removes the handoffs and approval gates between development and operations. Fast feedback catches a defect close to its origin, where it costs least to fix. Continuous learning makes experiments, failure and practice part of normal work.

The Five Ideals turn those ways into conditions a team can check in daily work. Locality lets a team change one part of a system without a committee meeting. Simplicity means fewer dependencies, not fewer features. Flow needs protection from interruptions, daily work needs time set aside to improve it, and psychological safety keeps defects and bad decisions visible.

The Engineering Manifesto names the values a team weighs, and the Architecture Principles turn those values into decisions about systems.

Start here

  • The Three Ways — Flow, feedback, and continual learning as a model for improving software delivery systems.
  • The Five Ideals — Locality, simplicity, focus, flow, improvement, and psychological safety as engineering conditions.

Resources

Posts

In this section

  • The Five Ideals

    The Five Ideals are the conditions that make fast flow real in daily work: locality and simplicity, focus, flow and joy, improvement of daily work, psychological safety, and customer focus. Where one is missing, engineers lose time to coordination, interruptions, hidden defects or work nobody needs.

  • The Three Ways

    The Three Ways are fast flow from development into operations, fast feedback that fixes quality at its source, and a culture of continuous learning. Together they describe how work should move through a software delivery system, whatever the stack, team size or decade.