Workshops are standalone, hands-on, paid programmes. Half a day at the shortest; two full days at the longest. Suitable for corporate cohorts that want a single concentrated learning event, or for open enrolment.
A workshop covers a topic completely — not as a teaser. Participants leave with the patterns, the code, and the confidence to apply it on Monday. Designed for working engineers who have a problem to solve, not a curriculum to complete.
Roughly half the time is on instruction; the other half is on practice — pair programming, exercises, and a small project that ties the material together. Every workshop ships with a workbook, a code repository, and a post-course assessment that you keep.
Run in open-enrolment cohorts (typically 8–20 participants) or commissioned by a corporate sponsor for an internal team. Corporate workshops can be tailored — the curriculum stays the same, the examples are adapted to your codebase.
| Title | Format | Duration |
|---|---|---|
| Building modular monoliths in .NET 9 | 2-day · Hands-on | 2 days |
| Production-grade React applications | 2-day · Hands-on | 2 days |
| Applied AI: orchestration patterns | 1-day · Workshop | 1 day |
| Continuous delivery for legacy systems | 1-day · Workshop | 1 day |
| Architecture decision records, in practice | Half-day · Workshop | 4 hours |
| Code review: a senior practice | Half-day · Workshop | 4 hours |
Hands on, end to end. Useful on Monday.