I can’t get into the audio versions of podcasts either – the whole listening while driving, or doing something else thing. My attention just wanders off.
I’m able to get through the video versions of the same podcasts better, where I can see their facial expressions, body language, etc.
But also, most podcast episodes feel longer than they really need to be… :)
CEOs are uniquely prone to AI psychosis because they’re sufficiently distant from the last mile of work that still has to happen to generate most value with AI.
So when they play with AI, they see the happy path results, often not considering the next 10 or 20 things that have to happen to get sustainable results from agents.
“Look I made this awesome product prototype”. Yes but you didn’t have to review the code before it went into production and fix a bunch of issues.
“Look I generated a contract”. Yes but you didn’t verify all the terms before it goes out to the counterparty and didn’t have to wire up all the past contracts to work with.
The best thing you can do as a CEO is to use AI a *ton* to figure out the real implications of agents in the enterprise, and come out the other side with an appreciation for both the upside and the real work that goes into them.
Today @GoogleMaps is getting its biggest upgrade in over a decade. By combining our Gemini models with a deep understanding of the world, Maps now unlocks entirely new possibilities for how you navigate and explore. Here’s what you need to know 🧵
the worst part about living in the bay area is you'll be having a perfectly pleasant conversation about kubernetes with your wife and then the table next to you will start posting your chat on x
I'm Boris and I created Claude Code. Lots of people have asked how I use Claude Code, so I wanted to show off my setup a bit.
My setup might be surprisingly vanilla! Claude Code works great out of the box, so I personally don't customize it much. There is no one correct way to use Claude Code: we intentionally build it in a way that you can use it, customize it, and hack it however you like. Each person on the Claude Code team uses it very differently.
So, here goes.
We often get asked – Why does Chip plug into an OpenTelemetry Collector, rather than pulling data from vendor APIs?
So we made a short video to tell you four reasons why. Check it out! (and enjoy the beats 🎶)
Presented a lightning talk about 🔄 Continuous Incident Readiness at a local SF meetup last evening.
Keeping your monitoring coverage up-to-date as new code gets written and systems evolve is a lot of manual work, and any misses can lead to blind spots.
We built Chip (@cardinalhq_io) to stay on top of it for you, so you’re always incident-ready.
Still drowning in incessant “🚨 High CPU!”-like alerts (or just muting your alerts channel entirely…I see you 🙈)?
It’s time for better alerts – ones that answer the two most important questions you care about:
➤ What's the impact on my customers?
➤ What caused this?
🎥👇
📢 Last week, we introduced Chip, the o11y/monitoring agent we've been building at @cardinalhq_io.
This ~30 sec clip highlights a common pain point we hear from high-velocity engineering teams, at companies both large and small, and how Chip uniquely addresses this need.
Stay tuned for upcoming content that will dive deeper, and follow @cardinalhq_io for updates!
👋 Hello, world. I’m Chip.
I watch your systems, spot issues before you do, and show up only when it matters — with the context your team actually needs.
Let’s make you incident-ready in minutes. 🎥👇