Systems | Development | Analytics | API | Testing

AI coding tool spend is projected to top $13 billion in 2026, compounding at more than 60% a year. These agents don't just autocomplete a line of code anymore. They plan. They act. They call tools, run commands, and touch other systems on your behalf. This is pretty different from the assistant that used to live in your IDE sidebar. And that's exactly where the risk lives. An AI coding agent is software that writes, tests, and ships code independently. This level of autonomy earlier tools never had.

That's a wrap on API + AI Summit 2026, Kong's biggest in-person event yet. The event brought together more than 1,000 engineers, architects, and leaders in Los Angeles to discuss running AI systems in production, tackle shared architecture challenges, and swap real-world insights. Recordings from this year’s event will be available in the coming weeks..

shoulda-matchers gives you one-line RSpec and Minitest matchers for common Rails behavior — it { should validate_presence_of(:name) } replaces a hand-written validation spec. Add gem "shoulda-matchers", "~> 8.0" to your Gemfile’s test group, then add the configuration block to spec/rails_helper.rb naming your test framework and library. Version 8 works with Rails 8.1 and rspec-rails 8.

How you store a streamed AI response decides what a client sees when the client joins partway through. A human agent taking over a support conversation, a refreshed browser, and a second device all need the response generated so far, and depending on how the response was stored, that late joiner gets the full response, fragments, or nothing. This article compares four common ways to store a streamed response, what each one gives a late joiner, and what each one costs your team.

You’ve probably encountered the online conversations about GitHub’s AI scaling challenges. A lot of the chatter is about how forgiving (or not) users should be to GitHub in light of inexorable traffic increases but also GitHub’s own decision-making. There is certainly irony in the fact that it was a swashbuckling GitHub, against the objections of many open source developers, that pressed Copilot on the industry.