The Modern Engineer's HandbookBuild · Understand · Ship
Saved0 Explore guides
THE FIELD GUIDE TO MODERN SOFTWARE ENGINEERINGVOL. 01

Build software.
Understand the systems.
Own the outcome.

The work behind the code—engineering workflows, AI-assisted development, debugging, shipping, and building products under real-world constraints.

Explore the handbookFind your starting point
◎⌘↗

15 practical guidesOpen knowledge. No account. No fluff.

change_request.mdFIELD NOTES
THE ENGINEERING LOOP
01UnderstandClarify the taskSTART
02InvestigateMap the systemTRACE
03Build + verifyUse tools with judgmentPROVE
04Ship + learnObserve the outcomeDONE ✓
LESS GUESSING. BETTER SYSTEMS.MEH / 001
✓Small diffReviewable change
Human judgmentAlways in the loop
SCROLL TO EXPLORE01 / THE PRACTICE
01Understand the system
02Use AI deliberately
03Ship with confidence
04Keep learning in public
HELP FOR THE WORK IN FRONT OF YOU

What are you trying to get done?

Start with the situation you have. Each route opens a practical guide, not a placeholder.

I was assigned a ticketClarify it, map the code, and plan a reviewable change.My API returns a 500 errorTrace the request to the first failing boundary.My local setup is brokenTrace the environment from setup instructions to runtime config.A CI check failedFind the failing step and separate code failures from runner issues.I need to review an AI diffCheck intent, edge cases, permissions, dependencies, and evidence.I am about to deployCheck build output, configuration, migrations, and the user path.I am stuck on a bugUse evidence to narrow the failure before changing code.I need to ask for helpShare what you expected, observed, tried, and need decided.A schema change feels riskyPlan a compatible migration and a recovery path.
Or use a bug report, task breakdown, or review worksheet
YOUR NEXT MOVE

What are you trying to get better at?

Pick your situation. We'll sketch a practical route through the handbook.

RECOMMENDED ROUTE0 of 5 complete

I am preparing for my first engineering role

Learn the habits that help you contribute to a real codebase.

    Your progress is saved on this device. No account needed.

    THE ENGINEER'S TOOLKIT

    Learn the work, not just the tools.

    Software engineering is a chain of decisions. Start with the part of the chain you want to strengthen.

    01

    Engineering workflows

    Turn vague tickets into safe, reviewable changes.

    3 guides ready
    02

    AI-native development

    Use coding assistants without outsourcing your judgment.

    2 guides ready
    03

    Quality & debugging

    Find the cause, not just a plausible-looking fix.

    2 guides ready
    04

    Delivery & operations

    Ship safely and learn from what happens in production.

    4 guides ready
    05

    Startup engineering

    Make good trade-offs when time and people are limited.

    1 guide ready
    06

    Engineering foundations

    Learn the fundamentals that make every tool easier to understand.

    3 guides ready
    A living knowledge base, built in publicBrowse every topic
    THE STARTER SHELF

    Guides worth keeping open.

    Written to be used mid-task: clear mental models, a repeatable workflow, and checklists you can take back to your editor.

    01 Engineering workflowsHow to Navigate an Unfamiliar CodebaseA repeatable first-hour workflow for understanding a repository before changing it—without reading every file or asking an AI to explain the whole thing. 9 minBeginner 02 AI-native developmentA Reliable Workflow for AI-Assisted CodingMove from prompt-and-pray to a deliberate loop: define the change, supply context, inspect the plan, implement in small steps, and verify the result. 10 minBeginner 03 Engineering workflowsYour First Engineering Ticket: From Request to Pull RequestA concrete workflow for clarifying a ticket, tracing the relevant code, making a small change, and showing evidence in a pull request. 10 minBeginner 04 Quality & debuggingDebug Software SystematicallyA practical incident-room method for reproducing bugs, narrowing causes, testing hypotheses, and preventing regressions. 9 minBeginner 05 Quality & debuggingHow to Review a Pull Request Like an EngineerReview the behaviour, risk, and maintainability of a change—not just its formatting. A practical checklist for human-written and AI-generated code. 8 minBeginner 06 Delivery & operationsFrom Engineering Ticket to ProductionFollow one change through the real software lifecycle: clarify the requirement, plan, implement, test, review, deploy, and observe. 10 minBeginner
    New to the handbook? Start with a real workflow, not a glossary.See the full index
    THE JUDGMENT GYM

    Knowing the answer is good.
    Knowing what to do next is better.

    Real engineering is rarely a multiple-choice exam. But quick scenarios are a useful way to practice the instinct behind a good decision. Pick your move, get the debrief, and take the reasoning with you.

    12scenarios
    04possible moves
    0accounts required
    AI JUDGMENT CHECKChoose your move

    The agent says “all tests pass.” Now what?

    A coding agent changed 14 files and reports that all tests passed. You did not see the test output. What is the most responsible next step?

    FIELD
    TEST
    THE PRACTICE IS THE POINT

    Be the engineer who can own the outcome.

    Start with one guide. Try one idea on a real task. Come back when the next question appears.

    Open the handbook