Systems | Development | Analytics | API | Testing

AI code generation is at a Pareto threshold. The first 80%—writing simple, functional snippets—is relatively straightforward. But the last 20%? That’s where it gets tricky. Building resilient, adaptable systems isn’t just a technical hurdle; it’s a leap of imagination and engineering, similar to the journey toward self-driving cars. Remember when everyone thought fully autonomous vehicles were “just around the corner”?

The emergence and growing adoption of generative AI and the agreement to and implementation of the EU AI Act uncannily coincided. These two factors have catalyzed an AI renaissance within many enterprises. Yes, companies were already applying AI here and there across their organizations — but responding to the impact of these two exogenous forces required a whole new way of thinking and doing. All of a sudden, all eyes were on AI.

The focus of this blog is to provide step-by-step instructions for deploying and configuring Kong Mesh with Kong Konnect on an AWS ECS instance so that anyone will be able to get pre-production installation of Kong Mesh standing up on their own.

I host two podcasts, Software Engineering Daily and Software Huddle, and often appear as a guest on other shows. Promoting episodes—whether I’m hosting or featured—helps highlight the great conversations I have, but finding the time to craft a thoughtful LinkedIn post for each one is tough. Between hosting, work, and life, sitting down to craft a thoughtful LinkedIn post for every episode just doesn’t always happen.

With its ability to link billions of objects and produce previously unheard-of volumes of data, the Internet of Things (IoT) has erupted onto the technical landscape. IoT is changing daily life and industries, from wearable and smart homes to industrial automation and linked cars. However, there are specific difficulties in guaranteeing quality, dependability, and security in this networked environment. Strong IoT testing is becoming essential rather than optional.

When building apps, it’s tempting to dive right into writing code. But if we do this, there’s a good chance that our code will eventually break, as new changes are made and new features are introduced. This is particularly true of React, a library that’s constantly evolving. Testing in React isn’t only about catching hidden bugs but also about maintaining code quality day-to-day.