Genki Nakamura

A migration can pass with the new build and still break a worker from the previous release that's finishing a queued job. Rename a column in one deploy, and that worker may keep writing the old name after the database has moved on.

Adding the new field first lets both versions coexist. Then you can backfill, switch reads, and remove the old field in a later deploy. The dangerous bit is declaring the old writers gone too early.

What do you check before that cleanup: running worker versions, drained queues, or logs showing no writes to the old field? If you run a small team, what's the smallest check you'd trust?

I'm in France, and I've spent the last twelve years designing and building WordPress sites for clients. I also make WordPress plugins.

I'm here to keep up with launches around WordPress and web design. If I leave a comment, it'll be an honest one.

Hi everyone

Every blocker I tried had a button to turn it off. And whenever work got hard, I pressed it.

I've been building apps for iPhone and Mac for years so I built my own: Cloister. It blocks distracting websites on your Mac and apps and websites on your iPhone and iPad. Once you start a block on the Mac, you can't switch it off until the timer ends. No Stop button, no "just five minutes".

It's launching here on Sunday, and I'll be around all day answering questions.