Best use of the day
Selective talks, quieter follow-ups, cleaner wrap-up
Saturday 2026-04-25
Use Saturday as a selective finish, not as an exhausted catch-up day.
Saturday feels lighter. Pick a few sessions you actually care about, use the quieter breakfast and lunch windows for better follow-up conversations, and leave with written notes instead of vague post-event optimism.
Priority order
- 1Choose 1 to 3 sessions you genuinely care about
- 2Use the quieter sponsor-floor windows for second conversations and follow-up checks
- 3Leave with structured notes before travel wipes out the details
Key windows
These are the blocks that should drive your day.
If time is short, prioritize these windows before optimizing anything else.
Breakfast and exhibition opening
Best low-noise window for a final sponsor pass or a calmer second conversation.
Lunch
Best midday wrap-up window for follow-up questions and useful final conversations.
Wrap-up and travel
The last conference sessions finish around 15:00, so use the transition out of the venue to write down what actually matters.
Timeline
Use the day as a sequence of decisions, not as a full schedule dump.
Every block below answers the same question: what should you do next if your goal is better signal and better conversations?
Time block
08:45
to 09:45
booth
Quieter breakfast, better conversations
Saturday opens more gently than Thursday or Friday. Use that to revisit the companies that still matter instead of doing another broad sweep.
Move: Favor second conversations over first-contact volume.
Time block
09:45
to 10:25
talk
Pick one architecture anchor early
This first block already offers a useful split between architecture, payments, and frontend crossover.
Move: Choose the room that best sharpens your actual post-event interests.
Time block
10:35
to 11:15
talk
High-value governance or security window
AI governance and Spring Security are both strong public-use choices if you want practical judgment rather than hype.
Move: This is one of the clearest Saturday room decisions.
Time block
11:25
to 12:05
networking
Keep the middle of the day flexible
Use this lighter block for mentoring, shorter conversations, or a reset before lunch instead of trying to optimize every minute.
Move: Preserve energy for one last good conversation at lunch.
Time block
12:05
to 13:05
networking
Lunch is your best final follow-up window
People are easier to catch, talk depth can go up, and you can close open loops before the last session block.
Move: Ask who you should follow up with next week, not just whether a company is interesting.
Time block
13:05
to 14:35
talk
Choose one last meaningful block
Saturday afternoon offers AI agents, soft skills, and software-design framing. Pick the one that best improves your own decision-making.
Move: Avoid collecting sessions for the sake of completion.
Time block
14:20
to 15:00
talk
End with one clean closing room or skip it
If you already have what you need, skip the last room and turn notes into a usable follow-up list before leaving.
Move: Protect the quality of your post-event memory.
Company targeting
Group the conversations so the floor does not become random.
These are not promises about booth location. They are the most useful conversation lanes to prioritize while the guide caveats still hold.
Revisit priority
These are good Saturday follow-up targets if they still look relevant after Thursday and Friday.
NetcompanyQualcoTeamViewerYodeckOpenBet
Enterprise wrap-up conversations
Strong choice if you want one more architecture-governance, banking, or transformation conversation before leaving.
Alpha BankEurobankDeloittePwCUni Systems
Sharper niche signal
Useful for security, AI-tooling, or platform-specific follow-ups when you care more about depth than breadth.
Hack The BoxHFMEPAM
Talk fallback
Use sessions as deliberate fallbacks, not as automatic defaults.
These are the smaller set of rooms most worth considering if the hallway, sponsor floor, or your energy level say it is time to step inside.
10:35-11:15Banquet Conference
What You Need to Know (And Why You Should Care) About AI Governance
A strong public-interest session if you care about AI governance without wanting a policy-heavy detour.
Why it matters: High value for anyone assessing practical AI leadership maturity.
09:45-10:25MC 2 Conference
Architectural Patterns for Spring Security You Wish Your Tech Lead Knew
Best early pick if you want a grounded architecture-security session with direct technical value.
Why it matters: Useful if your Saturday should skew practical rather than broad.
10:35-10:50MC 2 Quickie
Moving from blocking calls to Event-Driven Architecture
A compact event-driven modernization choice that fits well if you do not want to lose the full morning to rooms.
Why it matters: Quickies are ideal on a wrap-up day.
13:05-13:45Skalkotas Conference
Bringing AI Agents to Life: GenAIOps in the Real World
Best Saturday AI pick if you care about how agents move from demo to operating reality.
Why it matters: Strong bridge between AI interest and operational judgment.
13:05-13:45MC 2 Mentoring
Soft Skills and Career Development
Good choice if the most useful thing left is sharpening your follow-up and career narrative rather than adding another technical session.
Why it matters: Strong fit for a deliberate end-of-event reset.
13:05-14:35MC 3 Hands-on Lab
Software Design As Code
The strongest long-format Saturday commitment if you want one final deep design-focused block.
Why it matters: Worth it only if you are intentionally trading away floor time.
Practical tips
- Saturday is lighter, so conversation quality can improve even if total volume drops.
- The live Saturday content is exposed through a slightly odd schedule URL and page title, so rely on the session times and titles rather than the chrome around the page.
- If you pick the long Software Design As Code lab, accept that it becomes your main afternoon choice.
- Write the follow-up list before leaving the venue area; the value drops quickly once travel starts.
Conversation prompt
Saturday closer
Saturday conversations should be about closure: next steps, concrete team routing, and whether the earlier signal still holds up.
Before the event wraps, what is the cleanest way to follow up with the team or role that matters most from your side?
- If I follow up next week, who should I mention I spoke with here?
- What should I read or watch from your team before reaching out?
- Which role family here is most likely to match architecture-plus-AI interest?
Capture checklist
- Which companies still matter after all 3 days
- The strongest contact or routing path you gained
- One concrete next step for next week
- One talk idea or company signal that changed your assumptions
- What to drop so your follow-up list stays short enough to use
Reality checks
Saturday page chrome is misleading
The live schedule content is correct, but the page chrome still uses the older Thursday-schedule title format. Trust the dated Saturday content.
Lower volume changes the guide logic
Saturday is intentionally more selective. More sessions are available than you should actually try to consume.
Official links
Use these for the live schedule and public event context, then use this page to decide which move deserves your next block.
Continue