It didn't feel quite like a nightmare, but definitely woke up with a strange feeling.

2/2

Thus, at ACME Corp, a manager rubber-stamped a proposal he never saw, based on a report barely reviewed. It wasn't until months later that anyone realized that the company had deleted all its backups.

4/4

The engineer was happy to go back to vibe-coding, and put this bean-counting task behind him.
The manager was thrilled that the email volume requiring his attention was down to a trickle.

3/4

The engineer, buried under a mountain of tasks, had unleashed his own AI. It scoured cloud invoices, usage reports, company chat logs, seeking savings. The resulting report promised a 12% reduction by eliminating "dormant" storage.

2/4

AI Agent: That's a great suggestion!

Did you ever roll down a migration in production? How?

The deployed code has to have it, by definition, but if that code is running it also expects the migration to be up, right? Did you have a node with multiple versions? A special instance to run migrations?

While I listened to this it occurred to me: To boost RubyCentral membership for individuals, what if there was a badge that I could put on my blog, GitHub, or social that let others know I support RubyCentral financially?

Maybe it would encourage others to do the same, and boost participation.

👍 I guess I need to give it a try!

*backup service. 🤦‍♂️

Shout out to rsync.net. They are on top of it!