Migration

33 posts filed under Migration.

Count the places a job can be scheduled in your data stack. Include the cron on that one VM.

Before any stack change I ask how many consumers it touches and whether we can undo it by Friday.

The fastest tools in your data stack are written in a language nobody on your team writes.

I've worked with data teams where someone spotted the broken number first and decided not to mention it.

Senior data engineers quit stacks that page them at 3am, and the exit interview says "growth".

Nobody wants to be the one who questions the tool the last person bought before they left.

Every platform vendor offers 20-30% for an annual commit. The discount is real. The forecast underneath it usually isn't.

Data platform changes have a good window and a bad one. Funding milestones tell you which is which.

A company at 40 people needs senior data judgment about 2 days a week. Full-time is the wrong container.

Single-cloud is a fine strategy. Unpriced lock-in is a negotiating position, and not yours.

Want expert eyes on your data architecture?