Adam Savage is awsome.

Check out @IOUG's twitter feed for some of the highlights from Adam Savage's keynote. 

I hope I can find someone's video posted on YouTube, because it was particularly great, and far too much stuff to post as notes. If I find a link, I'll update this post. 

Comments

Post a Comment

Popular posts from this blog

What Free AI Is Actually Costing Your Organization

Image
AI tools are cheap to start using and easy to rationalize as low-risk. Most of them are free, or nearly free, at the individual level. No procurement cycle, no budget approval, no formal decision. That's precisely what makes the organizational cost easy to miss until it's already accumulated. This post is about what that cost looks like in practice — not in licensing fees, but in competitive position, organizational visibility, and the quiet dependencies that form before anyone thinks to ask about them. The cost of not deciding Organizations that are slow to adopt AI tooling tend to frame their hesitation as prudence. In some cases that's accurate. But there's a real productivity gap opening between teams that have integrated AI into their workflows and teams that haven't, and that gap doesn't pause while organizations debate governance frameworks or wait for the pricing model to stabilize. What I've observed is that the hesitation often isn't about skep...
Read more

The Signal Problem in Entry-Level Hiring

Image
The frustration is real. LinkedIn is full of it — entry-level roles requiring three to five years of experience, candidates rejected before they get a conversation, a generation convinced the door is locked from the inside. That frustration is worth taking seriously. But most of the conversation stops at the complaint. What's less discussed is the mechanism: why the mismatch exists, who's responsible for it, and what can actually be done. I've been on the hiring side enough times to know we're not blameless. What candidates can do with this If you're early in your career, the job description problem cuts in your favor more than you might think. Most postings describe an ideal candidate, not a threshold. If you meet the core requirements — the actual must-haves — apply. The worst outcome is silence, which you were already getting by not applying. The experience you have is probably more credible than you're presenting it. Internships, co-ops, serious side project...
Read more

Your Dashboard Is Not Observability

Image
A green dashboard and a healthy database are not the same thing. That distinction sounds obvious until you're forty minutes into an incident where every panel looks nominal and your storage layer is silently throttling writes for a specific tenant on a specific shard. That scenario is not hypothetical. It's the shape of the failures dashboards are structurally unable to surface — not because the tooling is bad, but because dashboards encode what you already know to look for. Observability is the capability to answer questions you haven't thought to ask yet. Those are different things, and treating one as the other leaves you blind at exactly the moment it matters most. Here's the structural problem: dashboards encode past hypotheses. That replication lag panel exists because you once had a replication lag problem. That connection pool chart was built after a connection exhaustion incident. The query throughput tile reflects the questions your team had during whatever po...
Read more