Engineering

A pattern where a stream-aligned team owns both its frontend and a use-case-specific backend, decoupling from shared platforms.

The C4 model organizes software architecture diagrams by nested levels of detail.

Consumer-driven contracts that replace coordination meetings between teams with automated integration guarantees.

A structured conversation technique for decomposing user story steps into concrete examples, rules, and open questions.

Opinionated but optional platform defaults that make the right thing the easy thing for stream-aligned teams.

Stream-aligned teams temporarily contribute to platform code when they need a capability, without creating a permanent dependency.

Two developers working at one machine, producing higher-quality code through continuous review and shared context.

Make an economic case for pursuing a process improvement or driving down toil using back of the envelope math.