What the job actually is, how software gets built by teams rather than individuals, and the vocabulary the rest of the roadmap assumes.
12 articles
Listed inWhat is a Software Engineer?Introductionon
The job is reading code, scoping work, and arguing about trade-offs — not typing. What to learn first, and what you can safely defer.
Listed inWhat is a Software Engineer?Introductionon
The engineer who designs systems that keep working after they ship, not just code that runs once.
Listed inRequirements and SpecsIntroductionon
Turning a vague request into something you can build, test, and argue about before writing code.
Listed inAsking Good QuestionsIntroductionon
How to get unblocked fast without burning a colleague hour, and what to try before you ask.
Listed inAgile and Its AlternativesIntroductionon
Scrum, Kanban, Shape Up, and waterfall — what each optimises for and the failure mode of each.
Listed inReading CodeIntroductionon
The skill you use more than writing: orienting in an unfamiliar codebase without reading all of it.
Listed inThe Software Development LifecycleIntroductionon
From problem statement to production and back again, and why the loop matters more than the phases.
Listed inCommon TerminologyIntroductionon
Idempotency, latency, throughput, coupling, cohesion, and the rest of the shared vocabulary in one place.
Listed inRoles and SpecialisationsIntroductionon
Frontend, backend, platform, infra, SRE, and mobile — what each one owns and where they overlap.
Listed inTechnical DebtIntroductionon
The difference between debt you took deliberately and mess you made accidentally, and how to pay down each.
Listed inEngineer vs ProgrammerIntroductionon
Where writing code ends and engineering begins: constraints, trade-offs, and responsibility for the result.
Listed inEstimationIntroductionon
Why estimates are always wrong, how to be wrong usefully, and what to do when the number is not believed.