The organization behind the Summit and SQL Saturdays is closing Jan 15 due to financial losses (PDF). The discussion to reinvent SQL Saturday is happening in the issues in this GitHub repo.
Wanna work there with Taryn Pratt?
I'm gonna be honest: if I had MySQL experience and a good Renegade, I'd apply for this job.
Class on deployment and governance.
Like Tim, I'm not a fan of reloading the same data every day. I mentioned this on social media, and a bunch of people said "but it's easy." Sure it is, but it doesn't scale.
Has turned out to be hard for PostgreSQL.
This design pattern is about ingesting a lot of rows quickly, then moving them off to normal tables later.
It's destroying SSD file systems.
Just can't argue with a good O'Reilly book.
