Classroom training for experienced engineering teams
I run focused, classroom-style workshops for software engineering teams that already deliver value but want to do it more consistently and with less friction.
Format
- 1–3 day workshops, on-site or remote.
- Small to mid-sized groups where active participation is expected.
- Mix of short theory blocks, code and architecture exercises, and guided discussions.
- Optionally tailored around your existing codebase, CI setup, and architecture challenges.
Who this is for
- Mid–senior software engineers who already ship to production.
- Tech leads and engineering managers responsible for standards and delivery.
- Teams who feel that "everyone does things slightly differently" and want a shared baseline.
Who this is not for
- Absolute beginners or bootcamp-style introductions to programming.
- Teams looking for generic motivational talks without concrete follow-through.
- Situations where there is no intent to change how the team actually works day-to-day.
Topics we can cover
- Engineering practices: code review, branching strategies, definition of done, and practical quality gates.
- DevOps practices: CI/CD pipelines, trunk-based vs. GitFlow in practice, and environments that support safe change.
- ADRs: when to write them, what to capture, and how to keep them lightweight but useful.
- C4 diagrams: using a shared visual language to reason about systems at multiple levels.
- Clean architecture: boundaries, dependency rules, and patterns that keep systems adaptable.
- AI-assisted engineering: integrating AI tools into your workflow to prevent technical debt accumulation, protect architectural boundaries, and support lightweight spec-driven development.
Engagement formats
- 1-day intensive: sharpening one or two focus areas for an experienced team.
- 2-day workshop: combining architectural topics (ADRs, C4, clean architecture) with delivery practices.
- 3-day deep dive: training plus guided work on your own architecture and pipelines.
Expected outcomes
- A shared vocabulary for architecture and practices across your team.
- Clearer, documented decisions instead of implicit, person-dependent knowledge.
- More predictable delivery because practices are consistent, not reinvented per feature.
- Concrete next steps tailored to your context, not a generic checklist.
What participants said
Feedback from a company development team after a 2-day, tailored system design workshop.
“Really great training, Krisztián is a really great trainer.”
“I like that we focused more on how to think rather than this is the right answer.”
„Ránk volt szabva, mégis általános patternekkel, megoldásokkal találkoztunk, amik bármelyik projekten hasznosak lehetnek.”
Translation: It was tailored to us, yet we came across general patterns and solutions that can be useful on any project.
“The best part for me was the reliability part. I was able to learn new terminologies and practices there which I haven't heard of yet.”
For training requests, a short description of your team, stack, and current challenges is more useful than a long RFP.
