The cruise ship has an itinerary. Every port scheduled, excursions booked, deviation is failure. You know where you're going before you leave. Waterfall. The plan is the product.
Wandering has a direction, not a destination. You follow what's interesting. The slug rename that spawned four draft posts. The Tapestry org that's still live from 2013. The realization that shortSlug and redirectFrom are the same thing. None of that was on the itinerary.
Most software teams want the Gantt chart but get the wandering, then feel bad about it. Agile tried to fix this by adding ceremonies to the chaos — standups to report on the wandering, retrospectives to discuss why it happened, sprint planning to project the next wander in advance.
The wandering style produces better journals. The cruise ship produces better Gantt charts.
The work today: rename a post, discover the slug is permanent, invent redirectFrom, generalize it to aliases, realize the journey block needs prev/next, sketch an SVG sitemap. None of it planned. All of it connected.
That's not a bug in the process. That's the process.
The journey
prev: chaos-development The work today was the example. Renamed a post, discovered the slug problem, invented redirectFrom, generalized it to aliases, sketched a sitemap graph — none of it planned. The itinerary didn't exist. The wandering produced more than a cruise would have.