Taught by peoplewho still ship.

You'll leave able to

• —Choose between static, server and client rendering for a given page, and defend it
• —Diagnose a Core Web Vitals regression from a real trace rather than guessing
• —Structure a codebase that survives four more engineers joining it
• —Ship an application to a real host with CI, not to a local dev server

Syllabus

1. Wk 1Rendering strategies and what each one costs
2. Wk 2Data loading, caching and revalidation
3. Wk 3Forms, validation and server actions
4. Wk 4State that actually needs to be client state
5. Wk 5Performance: measuring before optimising
6. Wk 6Accessibility as a build requirement
7. Wk 7Testing what's worth testing
8. Wk 8Deployment, CI and the first production incident

You'll leave able to

• —Build a retrieval pipeline and measure whether a change to it actually helped
• —Write evaluations before you write prompts
• —Control token cost and latency, and report both per feature
• —Decide honestly when an LLM is the wrong tool for a problem

Syllabus

1. Wk 1What the model is actually doing, and its failure modes
2. Wk 2Retrieval: chunking, embedding, ranking
3. Wk 3Evaluation harnesses and regression testing prompts
4. Wk 4Agents, tool use, and when to stop
5. Wk 5Guardrails, PII handling and data residency
6. Wk 6Cost, latency and self-hosting economics

You'll leave able to

• —Model roles and permissions without painting yourself into a corner
• —Design an audit trail that's useful in an investigation
• —Run a data migration from a legacy system without losing a row
• —Answer a security questionnaire with evidence

Syllabus

1. Wk 1Why enterprise software looks the way it does
2. Wk 2Roles, permissions and multi-tenancy
3. Wk 3Audit trails and immutability
4. Wk 4Dense interface design and keyboard-first workflows
5. Wk 5Migrations from legacy systems and spreadsheets
6. Wk 6Compliance: DPDP, GDPR and sector rules

You'll leave able to

• —Containerise an application and understand what each layer costs
• —Build a CI/CD pipeline from scratch and know why each stage exists
• —Set up monitoring that catches a problem before a user reports it
• —Read a cloud bill and reduce it deliberately

Syllabus

1. Wk 1Linux and networking you can't avoid
2. Wk 2Containers from first principles
3. Wk 3CI: building and testing automatically
4. Wk 4CD: deploying without downtime
5. Wk 5Infrastructure as code
6. Wk 6Observability: logs, metrics, traces
7. Wk 7Security basics and secret management
8. Wk 8Cost, and the incident you'll eventually have