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.

Loved this about pre-2022 Netflix engineering. End of a (glorious) era when they introduced levels/titles.

AI labs: We are very far but at the same time we are very close to reaching AGI

2026 is the year of unprecedented supply shocks – GPUs, HBM, NAND, and…San Francisco housing.

🤩

Poor Claude’s got a case of the Mondays too.

The Bay Lights are back! ✨

Good stuff! Looking forward to trying it out.

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.

Happy New Year! 🎉 Fireworks finale by the SF Bay Bridge 🎆🏙️

Chip ❤️ @OpenTelemetry

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.

If you're woken up by an alert in the middle of the night (been there, done that 😬), you ought to be able to get answers to these two questions, fast.

📢 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!

Turned my life upside down in 2023 (in a good way! 🙃) Let’s see what 2024 brings… 💪

Mood.

Oh, hey 1️⃣5️⃣ years. #MyTwitterAnniversary

✨ City lights ✨🌃

Japan Fall vibes. 🍁🍂 Golden Gate Park, SF.