@nathanlively.bsky.social

To carry 50,000 people per hour in each direction, a city needs a 175m wide road for cars. Even if those cars are electric. And then there’s all the parking. OR a city can move A LOT MORE people in a lot less space, with A LOT LESS public money, emissions, pollution, noise etc. Choices. Simple.

Graphic showing a 9 m wide track for metros can move as many people as a 175 m wide, 7 lane road for cars.

We all know a general session and a breakout. What do you call every other meeting/session happening as part of the conference that is bigger than a breakout, but is not the general session? A. Concurrent Session B. Ancillary Meeting C. Something else

This is a truly hands-on workshop, not an extended lecture. Bring your laptops and/or pair with others as you learn about #EventSourcing from scratch.

@dev2next.bsky.social · 2w ago

Curious about event sourcing but not sure where to start? 💭 Build a feature from the events up in this hands-on workshop with @ted.dev at #dev2next and see how event sourcing works in practice. 🔗 www.dev2next.com/schedule 🎟️ Get tickets: dev2next.com 📅 October 12-15 #EventSourcing #Java

Most production schedules treat the "Technical Needs" column like a dumping ground. When a project manager dumps an entire warehouse pull sheet into a single spreadsheet cell, the onsite crew stops reading it. Chaos follows at 7:00 AM.

> "The scary part is that I might lose some of this information." A multi-day, multi-room conference gets scheduled months out - across dozens of meetings and emails. Somewhere in client meeting #9 of 14, the keynote speaker mentions needing a headworn mic and wanting to walk out to "Happy.

Most developers expect a test to fail. Ted M. Young argues that the real value comes from predicting exactly how it will fail. When the result doesn’t match your expectation, you’ve uncovered a misunderstanding before it becomes a bug.

Six months before show day, your client mentioned her CEO always walks on to "Girl on Fire." It came up once. Near the end of a 40-minute call. You put it in the production schedule. On show day: right song, right moment. She didn't even have to remind you. Nailed it.

The production schedule isn't a pull sheet. That lives in your Lassos, Flexes, and Current RMSes. But, a production schedule can help highlight outliers and serve as a quick reference.

Bild

A production schedule that says "AV Tech" isn't a schedule for anyone. The moment you swap job titles for actual names - not "Sound Tech," but "Alex" - something shifts. The schedule becomes personal. Filter by name and a 50-row show collapses to the 11 rows that are actually Marcus's today.

BildBild

What if you sorted your production schedule by Day → Room → Time instead of Day → Time? You'd get something interesting. Instead of a show book where Room 1 and Room 3 and the Ballroom are all interleaved by clock... each room gets its own block. The manager still sees everything.

BildBild

Most production schedules are missing 3 columns. - Activity Phase (Setup / Show / Strike) - Filter and scan at a glance. - Technician (by name) - Everyone knows who owns what. - Technical Needs - Not a full pull sheet. Just the outliers: "2 Meeting Owls, hybrid webinar setup.

Bild

What exactly is a production schedule? aka show book, production bible, day sheet, master timeline In the event production world, I'd define it as the master operational document that coordinates your entire crew.

Testing Vaadin apps just got a lot cleaner 👀 Vaadin 25.2 introduces a redesigned Browserless testing API with: ✅ no mandatory base class ✅ cleaner locator syntax ✅ built-in multi-user support ✅ less boilerplate See what’s changing: vaadin.com/blog/a-more-...

Bild

Event sourcing without Axon or Spring Modulith -- here's what "just enough" looks like in Spring Boot. 👇 Write slices follow a simple 4-step pattern inside SliceCommandProcessor: 1️⃣ Load the stream-filtered history from a GigaMap in EclipseStore.

Bild

Here is my new anti-AI/Nathan-slop process for adding features to ShowBook: 1. Create a new "chapter" in the event model. 2. Put in the final UI screen I know I want to end up with (e.g., the final data grid with all 20 fields).

Bild

Last week, a "small" domain change in my app touched 99 files. Because I was using a single God Aggregate in Hexagonal Architecture, every change rippled to projectors, deciders, and UI. I thought this pain was just the trade-off of "good DDD".

I realized recently (from Ted Young) that I wasn't actually doing event sourcing in ShowBook. I was just doing CRUD with an audit trail. My initial, naive implementation was to create a command and an event for every single field in my domain.

Most Event Modeling examples are just UI loops, but middleware is all Translators & Automations. ⚙️ Here's my flow for a headless sync (A ➡️ B ➡️ C). I treat 3rd-party APIs as black boxes. Skip modeling their HTTP commands and point straight to the target event. How do you model yours?

Bild

I'm rebuilding ShowBook (again). I hit a wall wiring a massive 100-field UI to persistence and tried to let an AI coding agent brute-force it for me. It backfired. It just baked in "AI slop" and tech debt. New rule: small vertical slices using event sourcing.