Best use of the day
Balanced networking plus stronger talk value
Friday 2026-04-24
Friday is where the right room can finally beat the hallway.
Keep the big networking windows, but do not treat Friday like Thursday. This is the day where a few AI, architecture, and career-relevant sessions are strong enough to justify stepping away from the sponsor floor.
Priority order
- 1Keep the breakfast, coffee, and lunch networking windows intact
- 2Step into talks when they are clearly high-signal for AI, architecture, or career relevance
- 3Use afternoon decisions to balance one more sponsor pass against one more strong room pick
Key windows
These are the blocks that should drive your day.
If time is short, prioritize these windows before optimizing anything else.
Registration and breakfast
Fast floor scan plus first light networking before the keynote block begins.
Coffee break
Clean checkpoint to decide whether talks are outperforming the hallway.
Lunch
Best broad networking window on a more session-heavy day.
Coffee break
Useful reset before the last high-value afternoon sessions.
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:15
to 09:45
booth
Quick sponsor scan before the keynote block
Do one fast loop, confirm which companies still matter, then decide whether the keynote is worth taking in full.
Move: Keep the morning light; Friday is not the day to burn energy on a full floor crawl.
Time block
09:55
to 11:35
talk
Strong AI and product-process opening block
Friday opens with the keynote on keeping humans in the loop with AI coding agents, then moves directly into the spec-driven versus vibe coding debate.
Move: If AI working style is high priority for you, this block earns room time.
Time block
11:35
to 12:05
networking
First real networking checkpoint
Use the coffee break to compare notes, catch speakers or attendees, and decide whether to stay talk-heavy through lunch.
Move: Ask which sessions were actually worth the room versus just popular.
Time block
12:05
to 13:35
talk
Architecture and event-driven trade-off block
This stretch includes Kafka as a queue, event-driven architecture at scale, and career-relevant developer talks without forcing one dominant room.
Move: Pick one angle and resist the urge to chase every track.
Time block
13:35
to 14:45
networking
Lunch plus sponsor-floor reset
Lunch is still the best public networking window of the day, especially if you want one more company pass without losing every strong session.
Move: Revisit the companies that survived Thursday's ranking.
Time block
14:45
to 16:15
talk
Use quickies to sample signal without losing the whole afternoon
The quickie cluster lets you test architecture, modernization, and AI adoption themes in smaller doses than a long lab or keynote.
Move: Use one quickie and one hallway pass rather than chaining rooms for 90 minutes.
Time block
16:15
to 16:45
networking
Coffee break for the last routing decisions
This is the best place to decide whether the last session block or another conversation will create more value.
Move: Prioritize unfinished follow-up routes over casual wandering.
Time block
16:45
to 18:25
talk
Finish with a real choice, not default drift
Late Friday offers one of the strongest career-relevance talks plus a closing keynote. Choose intentionally rather than sliding into the nearest room.
Move: If you already have the networking signal you need, finish with one high-value session.
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.
Companies worth revisiting after Thursday
Friday is a better day for second conversations and clearer role-signal checks than for broad first discovery.
NetcompanyQualcoTeamViewerOpenBetYodeck
Architecture and enterprise-change conversations
Use lunch and coffee to test where architecture authority, governance, and platform ownership actually sit.
Alpha BankEurobankDeloittePwCUni Systems
AI, tooling, and product-platform conversations
Good if you want sharper signal on developer tooling, product engineering, or teams already using AI in public-facing ways.
Hack The BoxHFMTeamViewerEPAM
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.
09:55-10:45Banquet Keynote
Keeping humans in the loop with AI coding agents
The cleanest AI-working-style anchor of the day and a strong reason to be in a room early.
Why it matters: High signal if you care about guardrails, team process, and practical AI adoption.
10:55-11:35Banquet Conference
Vibe Coding vs Context Engineering vs Spec-Driven Development
Directly relevant if you want current language for how teams are actually structuring AI-assisted delivery.
Why it matters: Strong follow-on if the keynote already landed for you.
10:55-11:35Skalkotas Conference
Apache Kafka as a Queue: Bridging Event Streaming and Point-to-Point Messaging
A better room choice if architecture and integration depth matter more to you than AI process framing.
Why it matters: Useful for platform and enterprise-integration conversations later.
12:05-12:45Skalkotas Conference
Event-Driven at Scale: Evolving Architectures with Kafka, Java, and AWS
Strong architecture fallback when you want real systems signal without committing to a long afternoon room block.
Why it matters: Good bridge between architecture interest and later company conversations.
14:45-15:00MC 3 Quickie
Architecture vs. Headcount: Navigating the Sociotechnical Gravity of Mergers and Acquisitions
Compact but high-signal if you want a sociotechnical architecture angle without giving up the full lunch-to-break zone.
Why it matters: The quickie format makes it easy to pair with a hallway pass.
16:45-17:25Skalkotas Conference
But I Just Want to Write Code... Career Advice for Satisfied Developers
Best late-day pick if you want career signal without drifting into generic personal-brand content.
Why it matters: Strong finish if you care about career direction more than one last sponsor loop.
Practical tips
- Friday is the best day to switch between talks and networking without feeling like you wasted either.
- The FAQ still says room access is first-come, first-served, so do not over-plan tight room hops.
- Quickies are strategically useful because they let you sample a theme without surrendering a whole networking window.
- The live Friday schedule checked on 2026-04-23 does not show a Friday afterparty, even though the FAQ still mentions Friday evening.
Conversation prompt
Friday opener
Friday conversations can start from a session you just attended and then move into what teams are actually doing in production.
That session touched the kind of architecture and AI trade-offs I care about. Which teams here are actually applying this in production rather than just talking about it?
- Is that work sitting inside a platform team, product team, or central architecture group?
- Where are you seeing the hardest hiring gaps right now?
- Which conversations today would you tell a technical architect not to miss?
Capture checklist
- Company and conversation context
- Whether the signal came from booth staff, engineers, speakers, or peers
- What felt production-real versus aspirational
- The next follow-up step you can realistically take next week
- One reason to keep or drop that company from your shortlist
Reality checks
Schedule-vs-FAQ conflict still matters
The FAQ still references a Friday-evening afterparty, but the live Friday schedule checked on 2026-04-23 does not show one.
Sponsor-floor value depends on Thursday carryover
Friday company prioritization makes more sense if you already used Thursday to rank the booth and hallway opportunities.
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