Join me and my guest @ziniman, CEO & Founder of SpeakUp on May 14 at 9AM ET, while we discuss all things developer relations, and learn more about BoothLoader, which turns any conference booth into an interactive experience with games and live leaderboards, making attendees wanting to stop and engage while turning every event into measurable ROI. 👉 Link in the reply

Now in research preview: routines in Claude Code. Configure a routine once (a prompt, a repo, and your connectors), and it can run on a schedule, from an API call, or in response to an event. Routines run on our web infrastructure, so you don't have to keep your laptop open.

Generating code and verifying code are fundamentally different engineering problems. Good to see Claude Code recognizing the importance of review. And does it cost $15-20 per PR ?!@#? But the real question is: Should the same system that generates the code also verify it? In mature systems, we separate concerns:  • Creation systems → generation  • Integrity systems → quality, governance, verification, observability They operate on different philosophies:  generation optimizes for output, verification for skepticism. Speed is easy. Quality is the hard part. And as code generators evolve, teams will want the freedom to switch between them. That’s why we believe the winning stack will look like:  Claude Qodo = speed quality = velocity  (Claude reviewing Claude risks shared blind spots and even $$ spend?)