Library

The five rules every Developer Dojo member follows, in plain words.

Why a human, not an AI, must write the epics and the roadmap, and what AI may still do.

Why plans, decisions, content and settings live in git, and what that means every day.

Look for existing open source before you build, and check the licence every time.

When something breaks, ship a new fix. Do not undo shipped work to make the problem disappear.

Say when and how you used AI. Honest use is welcome. Hidden use is the problem.

The six-week plan to own one product from first customer talk to a final Product Package.

Draw your product on one page, list every part, and start talking to customers.

Interview users, write personas, map touch points and draw user and customer journeys.

Turn the gaps in your journeys into a roadmap of 4 to 8 epics that you write yourself.

Check dependencies, map stakeholders, defend your choices, and learn to steer AI agents with agent-ready epics.

Choose a brand name, publish a simple product website, and draw mockups of the next version.

Write your Product Catalogue, record a demo, and present your Product Package.

What the final Developer assessment contains and how to prepare it.

The six skills and the scoring levels used to assess your Product Package.

A simple weekly rhythm for an epic manager, and the mistakes to avoid.

What a Master Developer knows beyond the Developer path: the platform, production launch and AI-agent orchestration.

The shared ground under every product, explained by the job each part does.

A repeatable way to decide between using, patching and building: search, scorecard, fit score and decision record.

The licence families, the traps (especially network copyleft), and how to check a licence.

How to adopt an open source project, keep your own changes small, and keep following upstream.

Run infrastructure and applications from git, keep secrets out, and find and close drift.

ITIL ideas (catalogue, change, incident, service levels) done with merge requests, issues and files.

Gates, practical tasks and the oral review used to certify a Master Developer.

A four-layer way to describe a product: Master, ORBITAL, ANDROID and Tech, plus a catalogue entry for each service.

What a good epic contains, how big it should be, and how to write one.

How to build, present and keep a roadmap true.

How to split a product into repositories, name them, and describe each one.

How to run a whole-product plan with issues, milestones and labels, on a free git account or a paid one.

Copy-ready templates for the Developer path and the Master Developer rank.

A one-page brief that says why a product exists, who it is for and what success looks like.

A demographics sheet and a one-page persona, with known and guess marks.

Three tables: touch-point inventory, user journey and customer journey, with a bridge to your repositories.

One table that lists every repository your product needs, with owner, kind and status.

A table of every outside tool your product uses, who it serves and what data moves.

Write one epic by hand and lay your epics out as a roadmap.

A short record of a tool or design decision: what, why, alternatives, licence, exit plan.

A small file that describes one product or service: owner, tier, repos, dependencies and service levels.

A merge request template that records the reason, risk, recovery plan and checks for a change.

A short note that tells your sponsor or coach the truth about the week.

A curated list of free learning resources, grouped by week, and how to pick from it.

Free reading and courses for the Developer path: roadmaps, personas, journeys, epics and cloud basics.

Free documentation for the Master Developer rank: delivery from git, licences, infrastructure as code and service management.

Courses and certificates that may cost money. None are required.

Plain-English meanings of the words used across the Developer Dojo library.

Run your app on your own laptop the same way it runs in production, using GitOps, containerd and local Kubernetes.