Teach a move, not a slogan.
Every guide should help a reader do something: investigate a bug, structure a task, review a change, or make a decision.
Software engineering is more than writing code.
This handbook is an attempt to make the real work of building software easier to learn: the workflows, judgment calls, tools, collaboration, and operational habits that sit around the code.
01THE THESIS
Connect the classroom to the codebase.
Traditional computer science knowledge matters. Algorithms, data structures, databases, networks, operating systems, and programming fundamentals help engineers reason about systems. But knowing concepts in isolation is not the same as knowing how to make a safe change in an unfamiliar repository, debug a production issue, or choose a pragmatic architecture for a small team.
AI coding tools are changing how software gets produced. They can accelerate implementation and exploration, but they also raise the importance of context, verification, review, and clear ownership. The handbook focuses on those durable skills without pretending that tools remove the need for engineering judgment.
02THE METHOD
Show the reasoning.
Separate observed facts from assumptions. Link to authoritative references and be honest about trade-offs.
Keep the human in charge.
AI can help produce options. Engineers remain responsible for checking them and understanding what gets shipped.
03THE PROMISE
“Learn the fundamentals. Understand the system. Use the tools. Verify the result. Own the outcome.”
This is an evolving educational project, not a claim that one guide can replace experience or mentorship. Tool-specific pages carry review dates, but those dates are not a claim of outside expert review. Corrections and concrete examples are welcome.
Explore the handbook