Human-First Engineering

Growing engineers in the age of AI.

What happens to software engineering when we can generate code faster than we can understand it?

For most of our industry’s history, the limiting factor has been writing software. Every generation of tooling — compilers, higher-level languages, IDEs, autocomplete, static analysis — has chipped away at that friction. AI is the next step on that same ladder.

But it is a step change in degree. For the first time, the bottleneck is not producing code. It is understanding it. The cost of generating solutions has collapsed. The cost of validating, reasoning about, and trusting them has not.

That tension does not just affect code quality. It affects people. If we are not deliberate, we risk a generation of engineers who can assemble systems without ever building the mental models behind them — and a pipeline from junior to senior to principal that quietly erodes.

This site is a lightweight response to that risk: a manifesto, a framework, and a practical guide for putting both into practice.

Read the documents

• The Manifesto — what we believe, and why.
• The Framework — how we work in practice.
• The Toolkit — implementation guide, practices, talking points, slide deck, and developer FAQ for putting it all into practice.

The one-line summary

AI is the next step in a long history of assistive tools — and we use it to grow engineers, accelerate delivery, and protect quality.

Version

This is 1.0.0 of the Human-First Engineering manifesto, framework, and toolkit. See the changelog for the full history.

License

This work is licensed under CC BY-NC-SA 4.0. Share freely. Build on it. Don’t sell it.