CircleCI

Hot take from @lucaronin: maybe code review wasn't working all that well before AI either. 👀 New Confident Commit with @z00b: circle.ci/4vWHomu

"Someone just pointed a blowtorch at your playbook." New convo with @z00b & @DevInterrupted on leading engineering teams through AI, the future of PRs, and why the old workflows won't survive. youtube.com/watch?v=-ihKWE…

What does it cost to validate and ship code at an agentic pace? For a 50-dev team, validation-related delivery costs can approach $900K a year. 😳 We break down why the teams pulling ahead are moving validation earlier: circle.ci/4xb7Dqt

What keeps someone in tech excited after all these years? For Jun, it's helping engineers build great software. Learn more about the people behind CircleCI: circle.ci/4eP37Gn

Every line of code is risk. AI makes it easy to write more code, but is that always a good thing? Learn more: circle.ci/4exRPGv

The question isn't whether your proposal is good, it's whether it's more important than everything else competing for the same time, people, and budget. That's why the strongest proposals explain the impact, not just the work. More insights from @z00b: circle.ci/4xmUXNZ

Runs, jobs, step output, test results. All from the terminal. The new CircleCI CLI brings interactive debugging, predictable JSON, and built-in MCP support for coding agents directly into your workflow. Learn more ⬇️ circle.ci/4y7ZiVG

45.6 seconds from scratch. 12 seconds with a snapshot. 😎 Here’s what happens when you stop rebuilding the same environment every time ⬇️

The best part about a great career? There's always something new to take on. After six years at CircleCI, Tim's still finding new ways to bring our community together through the events he leads. Learn more about how our team has grown at CircleCI: circle.ci/4eP37Gn

What do teams shipping 9x more validated code have in common? 1️⃣ More finished work per engineer 2️⃣ Validation beyond the push 3️⃣ Fewer cycles per shipped change The data behind the habits: circle.ci/4rjo5SG

The latest data is in! The State of Software Delivery Pulse Report looks at what changed over the last quarter, what the highest-performing engineering teams are doing differently, and why the performance gap is continuing to grow. Read on: circle.ci/4aLa7mG

Hook Claude Code up to CircleCI and tell your agent to fix the failing tests and don't come back until the build is green 🟢 Full tutorial: circle.ci/3T4p5xT

When AI generates code and an incident hits, who speaks to what it was supposed to do? When that line blurs, debugging gets really hard, really fast. Watch the full convo: circle.ci/4exRPGv

Last year, she was standing on stage as the Wearable Tech Challenge winner. Now, she’s back as a judge. 💚 Watching students keep exploring, building, and growing long after the competition ends is what it's all about. We can't wait to see what she does next!

Technical proposals can be like campfire stories. You start at the beginning, walk through every discovery & technical detail, and eventually arrive at the point. The problem? By then, you've lost the audience. More from @z00b: circle.ci/4xmUXNZ

The inner loop is getting smarter, and it's putting pressure on everything downstream. @z00b joined @TechStrongTV to talk about what that means for CI/CD. 👀 circle.ci/4vF93ZV

Same repo. Same tasks. Same validation gates. The only difference? Where validation happened. Here's how Chunk sidecars returned feedback in 22 seconds versus about 69 seconds through a traditional CI pipeline. Full demo: circle.ci/4wiqTSu

A concerning amount of AI software is making it to production via ~vibes~ More from @seldo and @z00b: circle.ci/4ek2PbC

The faster AI writes code, the shorter the feedback loop needs to be. Chunk sidecars bring fast validation into AI coding workflows, helping agents fix issues before code reaches a CI pipeline. Thanks to @InfoQ for covering! circle.ci/3T1V2a1

Your CI pipeline wasn't built for agents running hours-long tasks. We break down what that means for validation infrastructure ⬇️ circle.ci/4ostE0K