Systems | Development | Analytics | API | Testing

Every Next.js application has to deal with errors, whether it's a failed API call, invalid user input, or a bug that slips into production. The App Router gives you built-in tools to handle each of these cases differently, keeping your UI intact and your users informed.

Token costs used to be something most developers ignored. They simply dismissed them as theoretical. Now, they’re showing up in your Cursor/Claude Code bill, in every pasted error, in that package the AI pulled in without asking, or in that clarification round you didn’t plan for. Most developers choose a framework based on what they've used before, what the job description asks for, or simply whatever was used on their last project.

A growth forecast is only useful if your business can deliver on it. Many PropTech companies project ARR growth without fully accounting for the systems, integrations, implementation capacity, and engineering effort required to support it. The result is predictable: sales targets are met, but delivery teams struggle to keep pace. The strongest forecasts connect revenue goals with operational reality.

When we develop applications, we sometimes only focus on the “how”—how to build the processes, how to architect the data structure, and how to encode the correct logic. But for users, the "what" is their reality—and sometimes that’s overlooked during development. An application that looks and feels like your brand identity isn't just visually appealing. It builds trust, reduces cognitive load, and makes your application more enjoyable for your users.

I ran a webinar on this recently and had more to say than the time allowed, so this is the written version: the argument I was making, some context on the demo, and the questions that came up from people watching. The recording is below if you'd rather watch than read. The thesis: AI products are being let down by the user experience, not the model.

Since the first vehicles were rolled out to customers, automakers have competed to deliver the newest features and the greatest benefits to the driving experience. Today, that competition is less about shaping a car’s physical characteristics and more about making cars smarter and more connected to the world around them. With thousands of car models and trim levels available worldwide, there is a fierce need to find new ways to stand out from the competition.

Have you ever launched an enterprise application that sailed through every baseline test, only to falter when confronted with real-world demand? When you’re modernizing critical workflows for a major financial institution, a “good enough” architecture is a ticking time bomb. In high-volume operations, performance failures aren't just minor setbacks—they halt transactions, stall back-office teams, and expose the business to significant operational risk.

Version v0.2.0 of @ably/ai-transport reorganises the SDK to better support a wide range of interaction patterns. Everything in an AI session – input, output, agent lifecycle, control signals – is captured durably, allowing you to easily build the sophisticated interaction patterns that support modern AI user experiences. When we first built @ably/ai-transport, we modelled an AI conversation the way most people first picture it: as a request and a response.

AI agents move fast. Securing them shouldn't slow you down. Kong and Noma are partnering to change that. This program delivers high-quality, reliable integrations providing real business value for customers..

console.log() is a foundational tool for developers learning JavaScript. It sends messages to the browser’s DevTools console, so we can see what our code is doing at runtime. This allows us to: Because it prints information directly to the console, we can observe values, program flow, and potential issues. In this post we’re going to cover the basics of console.log() syntax, the nuances of formatting and the essential DevTools add-ons that turn console.log() from a window into a dashboard.