📋 BUSINESS CASE TOOLKIT
Convince Your Boss
Everything you need to make the business case for sending your team to From Lizard to Wizard .
Talking points, ROI math, and an email you can copy-paste.
⏱ 4 hours · 💶 €299 / engineer · 🌐 Remote
STEP 01
Does your team need this? Answer honestly. If you say "yes" to two or more, this workshop probably pays for itself in the first month after.
▸ Has your team shipped a system that needed to be partially rewritten within 12 months? ▸ Do production incidents take longer to debug than they should because of missing instrumentation? ▸ Is "I'll add tests later" a phrase you hear regularly? ▸ Has an architecture decision in the last year cost you weeks of unplanned engineering work? ▸ Are design pattern discussions in code review either non-existent or always escalating? STEP 02
Build your pitch
Pick the topics you want to learn, add your details, hit copy or open it straight in your mail app.
Everything updates live below.
🏛 Frontend System Design The RADIO framework — structured walkthroughs for system-design interviews Architecting a real-time chat app: virtualization, optimistic updates, WebSocket reconnection, typing indicators, offline queue Folder structure that scales — feature-based vs atomic, when to switch State management decision tree — useState, Context, React Query, Zustand Cursor-based pagination + scroll-position management Normalized state shapes so the same message never lives in two places
🧩 Microfrontends & Module Federation The 4 real reasons companies adopt microfrontends Vertical vs horizontal architecture — which one to pick for your team's shape Module Federation deep-dive — dependency sharing, runtime loading, shared singletons Inter-microfrontend communication: query params, broadcast API, shared event bus, "brain" microfrontend Bounded contexts + Conway's Law applied to frontend org charts The smell that means microfrontends are wrong for your situation
🛰 BFF & Server-Driven UI Server-driven UI: when the backend shapes what users see Designing the render contract between server and client Driving navigation, analytics, and A/B tests from the backend The line between SDUI and "downloading code" — Apple and Google's rules Backend-for-Frontend: when a tailored gateway pays for itself Live config updates without WebSocket complexity
⚡ Event-Driven Architecture The event bus pattern — when it saves you, when it betrays you Decoupling cross-cutting concerns (notifications, analytics, audit trails) Pub/Sub for inter-microfrontend communication without a global store Frontend event sourcing — yes, really, and when it's the right call Replayability + time-travel debugging from your event log Testing event-driven flows without mocking the entire universe
👁 Frontend Observability Logs vs metrics vs traces — what each one is actually for Instrumenting a frontend with OpenTelemetry end to end SLOs and SLIs that don't page on noise Distributed tracing across microfrontends — yes, this is hard, here's how Real-user monitoring (RUM) vs synthetic monitoring — both, neither, when Walking through a real production incident together
You also get — always included
Bonus deck: Accessibility deep-dive (WCAG, ARIA, inclusive design) Bonus deck: Security essentials (XSS, CSRF, CSP, auth patterns) Bonus deck: Design patterns (creational, structural, behavioral in React) Full workshop repo — every line of code we write together All slides, every project — complete reference material Discount on any future courses or workshops Your name Your work email Manager's name Manager's email
📋 Copy email ✓ Copied! ✉ Open in email client ✓ Opened
👉 Pick at least one topic to generate your email.
STEP 03
The math is embarrassingly simple One avoided rework, one prevented incident, one cleaner architecture decision — and this is already a win.
What it costs Workshop ticket €299 / engineer Time investment 4 hours (1 evening or morning) Remote — no travel costs €0 Comparable training €1,500 – €3,000 What it saves One avoided 2-week rework ~€8,000+ Faster MTTR on one P1 incident ~€5,000+ Engineer onboarding speedup Days, not weeks Fewer "I'll fix it later" tickets Compounding Translation for your boss: the workshop pays for itself the first time it prevents one bad architecture decision. Everything after that is profit.
Boss said yes? Lock it in. One session — Thursday, May 28, 2026. Limited seats. Once it fills, that's it.
Save your seat →
Thursday May 28, 2026 · 5–9 PM CET time · 4-hour intensive · Remote
