2 days · Budapest · June 11-12 (Thu-Fri) · small group · in person only
Become the developer who can reason at system level.
Sound familiar?
- Architecture decisions fall apart in meetings.
- There is no shared language for diagrams.
- It is hard to explain why you chose this direction.
- ADRs exist… but nobody reads them.
Then this workshop is for you.
Only 7 seats left
After registration, you are redirected to a secure Stripe checkout page. You will receive an immediate email confirmation about successful payment and the next steps.
100+ positive feedback on earlier materials → now in live workshop format
What you actually get
- A working method so you do not make architecture decisions on gut feel alone.
- Tools to defend your decisions when conversations get contentious.
- Modeling practice that others understand the first time they see it.
- Confidence the next time someone asks, “why this way?”
What you take home
- When you are stuck choosing between three options, you will have a structure to decide.
- When someone asks “why this way?”, you will not freeze.
- You learn to model the system so anyone—from the CEO to a junior—can understand it.
- When you need to document a decision, you will not be filling in an empty template.
About the instructor
Krisztián is a software architect and consultant with over a decade of hands-on experience in designing, building, and evolving complex software systems. After years in senior engineering leadership roles, he founded his own consulting company, where he helps organizations modernize their architecture, accelerate delivery, and build sustainable engineering practices.
He specializes in cloud transformations, DevOps practices , architectural decision-making ( ADR ), and pragmatic system design. Krisztián is also the founder of the Letscode.hu community , creating a supportive environment where individuals can thrive, share their knowledge, and collectively contribute to the advancement of technology. The Letscode.hu podcast stays in the same lane—shorter episodes and more conversational angles—and you can tune in on SoundCloud .
Frequently asked questions
Who is this workshop for?
This workshop is for developers who want to think at system level—not only ship code.
If you have worked on real production systems and want to make better decisions around architecture, trade-offs, and complexity, it is for you.
Do I need prior experience?
Yes—basic professional development experience is required.
It is not for absolute beginners, but you do not need to be senior. What matters is that you have faced real problems, not only tutorials.
How many people can attend?
Minimum 6, maximum 10 participants.
We keep the group small so you can ask questions and discuss—not only listen passively.
Where and when is it?
In person in Budapest (District XIII). June 11-12, 09:00-17:00.
Venue: Ruander Training Center, District XIII, Frangepán utca 3.
What happens after payment?
Right after payment you receive a short questionnaire so we can tailor the content even better.
If anything changes, we will notify you via email.
Can I get an invoice for my company?
Yes. During checkout you can enter the required billing details, and we will issue the invoice accordingly.
What if I cannot attend?
In short, if you cannot attend:
More than 10 days before the event: 100% refund.
Between 7 and 10 days before the event: 50% refund.
Within 7 days or in case of no-show: no refund.
Your ticket is transferable, and late arrival does not qualify for partial refund.
Full text and all clauses: Terms & Conditions
What if the workshop is cancelled?
If we do not reach the minimum headcount, we reschedule the workshop or refund the full amount.
Will there be a recording?
No. This is an interactive, in-person workshop—not a lecture.
That interaction is where most of the value comes from.
What will I learn in practice?
We work through real examples: system design decisions, understanding trade-offs, typical pitfalls and how to avoid them.
It is not a theory-only talk—it trains how you think.
If this is relevant now, don't postpone it
Seats are limited: 99,000 HUF until May 17, then 119,000 HUF. Date: June 11-12 (Thu-Fri).
Only 7 seats left
After registration, you are redirected to a secure Stripe checkout page. You will receive an immediate email confirmation about successful payment and the next steps.
Detailed schedule
Day 1 — Decisions and ADRs
- 09:00 – 09:20Introduction
Short intros and context. You walk through the workshop arc: from a problem to a decision, then to documented change.
- 09:20 – 10:30Structuring decisions
You learn to state a problem clearly, surface options, and decide along trade-offs. You run through one shared example together.
- 10:45 – 12:15Your own decision situations
You work on your own problems. The goal is that everyone leaves with one concrete, explicit decision.
- 12:15 – 13:15Lunch
- 13:15 – 14:00ADR fundamentals
How a decision becomes short, readable documentation. What to focus on—and what is just noise.
- 14:00 – 15:30Writing ADRs
You turn morning decisions into ADRs. This is where it shows how clear the decision really was.
- 15:45 – 16:30Review and refinement
You read each other's ADRs, ask questions, and tighten wording so others can follow it.
- 16:30 – 17:00Closing
You recap the day and how decisions shifted while writing them down.
Day 2 — C4 and systems thinking
- 09:00 – 09:15Warm-up
Brief bridge from day 1: you have decisions and ADRs—now you look at their impact at system level.
- 09:15 – 10:30Understanding the system
How to look at a system as the outcome of decisions. What belongs in the picture, what does not, and what makes it legible for others.
- 10:45 – 12:15C4 essentials
The core of the C4 model and how to present the system at different levels.
- 12:15 – 13:15Lunch
- 13:15 – 14:30Shared modeling
On one example you sketch the system together, focusing on architecture that is easy to communicate.
- 14:45 – 15:45Visualizing your own system
You draw your own systems. This is where “communicable architecture” becomes concrete.
- 15:45 – 16:30Presentations and feedback
You show diagrams to each other and give feedback on clarity and usefulness.
- 16:30 – 17:00Connecting the full flow
You tie it together: problem, decision, ADR as change, and the current system state in C4.
