The scheduling tool went live this morning, and a conference that had been an abstraction for months turned into a grid with my name on it. Favoriting sessions is the easy part — I'd done the reconnaissance weeks ago, so this was mostly clicking "yes" on decisions already made. What the grid revealed, once it filled in, was the actual shape of the week. And the shape has two immovable objects in it: a hackathon on Monday night and a certification exam on Thursday afternoon. Everything else arranges itself around those two.
This post is the game plan. Not the session-by-session catalog — that's coming when I do my full picks — but the strategic layer above it. How do you survive a four-and-a-half-hour build sprint that ends near midnight on day one, and then walk into a proctored exam three days later still sharp enough to earn the score you came for? You plan the collision out of existence before you land in Las Vegas.
The two hardest things I'm doing all week sit at opposite ends of it. The trick isn't surviving either one — it's making sure the first doesn't cost me the second.
Monday — Endurance Day
Monday is the one that will test me physically more than intellectually. It opens with a 9 AM session and, if I let it, runs unbroken into the VMware {code} Hackathon at 7 PM, which itself runs until 11:30. That's a fourteen-and-a-half-hour day, and the most demanding block is the last one.
Sessions front to back through the afternoon, then the Welcome Reception at 5 PM, then the {code} Hackathon from 7:00 to 11:30 PM. The reception isn't optional networking — it's my dinner. The hackathon runs on adrenaline and whatever food you remembered to eat beforehand, and I have watched too many good teams fade at hour three because nobody ate. This year I eat at the reception, deliberately, like it's part of the build plan. Because it is.
The hackathon is the centerpiece of everything I've written in this series so far — the MCP-powered conversational layer over infrastructure data, the 2 AM on-call problem, the whole premise. Monday night is when the concept meets a four-and-a-half-hour clock and a room full of people who've done this before. Win or lose, it's the best story of the week, and I'll be taking notes the entire time.
Tuesday & Wednesday — Session Days
The middle of the week is where the exam prep hides in plain sight. Back in my Cert Prep Map post, I named the two domains I'm softest on for the 2V0-16.25 exam: vSAN, and what the blueprint still calls Aria Operations — now VCF Operations. When I went hunting the catalog, I made sure the sessions that touch those two domains landed on Tuesday and Wednesday, so the material would be freshest right when I need it.
Opens with "What Is MCP and Why Does It Matter" at 9 AM — which is either reinforcement or redemption depending on how the hackathon went the night before. A perfect morning-after pairing either way. The rest of the day is VCF architecture and private cloud sessions, building the platform context the storage and operations material sits on top of.
The gap-closing day. "Optimizing Virtual Storage and vSAN" at 9 AM and "Autonomous Rightsizing and Capacity Planning" at 4:30 bracket the day with exactly the two domains I flagged as weak. This is the last full day of content before the exam, and it's aimed squarely at my soft spots by design. Wednesday evening, though, I rest. The temptation on the last big night is to close down the show floor. The exam the next afternoon says otherwise.
Thursday — Exam Day
Here's where the schedule did me a quiet favor. Thursday, the last day, showed "No Sessions Available" when I first looked at the grid — a nearly empty day. That empty day is now my exam day, and the emptiness is the point. I sit 2V0-16.25 at 3:30 in the afternoon, at the VMware Exam Center on-site, having just spent two days absorbing precisely the vSAN and VCF Operations content I most needed. No competing sessions, no clutter, nothing between me and the material but a clear morning and a walk to the testing room.
If you're sitting a certification exam at the event, confirm every detail of the appointment in the testing portal before you travel — the exact date, the start time in local Las Vegas time, and the on-site center location. The exam is booked separately from your session schedule, and it's the kind of thing that's easy to assume is handled and worth verifying anyway. A few minutes of double-checking now buys a clear head on exam day.
The plan for Thursday morning is deliberately thin: light review, a walk through the expo floor, maybe one Hands-on Lab if something calls to me. Nothing back-to-back. I passed 2V0-12.24 with a perfect 300 last cycle, and I didn't do that by walking in frazzled. A clear head is part of the preparation, not separate from it.
Why the collision matters
It would be easy to treat the hackathon and the exam as two unrelated items on a list. They're not. The hackathon is a late night that could bleed exhaustion into the rest of the week if I let it. The exam is a performance that demands the opposite of exhaustion. Left unplanned, the first quietly sabotages the second. So the plan is simple in shape: go all-in on Monday night, absorb hard on Tuesday and Wednesday, protect Thursday morning like it's sacred, and don't let the fun of the front half borrow against the focus the back half requires.
That's the whole strategy. Front-load the intensity, protect the exam, and eat something before the hackathon.