In my experience with mobile development, I’ve seen how apps become increasingly complex and projects grow uncontrollably. I remember perfectly that feeling of having thousands of lines of code and not being sure what was really being used and what wasn’t.

That’s why I was so struck by the tool that Sentry (formerly from Emerge Tools) just released as open source: Reaper. An SDK that does something that sounds simple but is tremendously useful: find dead code in your mobile applications.

A few years ago, many AI researchers (even the most reputable) predicted that prompt engineering would be a temporary skill that would quickly disappear. They were completely wrong. Not only has it not disappeared, but it has evolved into something much more sophisticated: Context Engineering.

And no, it’s not just another buzzword. It’s a natural evolution that reflects the real complexity of working with LLMs in production applications.

From prompt engineering to context engineering

The problem with the term “prompt engineering” is that many people confuse it with blind prompting - simply writing a question in ChatGPT and expecting a result. That’s not engineering, that’s using a tool.

Deno 2.4 has just been released, and I must admit it has pleasantly surprised me. Not only because of the number of new features, but because of one in particular that many of us thought would never return: deno bundle is back. And this time, it’s here to stay.

This release comes packed with improvements ranging from importing text files directly to stable observability with OpenTelemetry. Let’s explore what this release brings us.

I’ve seen how certain standards and tools become indispensable when working with data. And if there’s one thing we’ve learned over these years, it’s that JSON is everywhere: APIs, logs, configurations, NoSQL databases… The question is no longer whether you’ll work with JSON, but when you’ll face that 15-level nested structure that makes you sigh.

The Problem We’ve All Lived Through

How many times have you had to write something like this?

The first alpha version of PHP 8.5 has just been released, and I must confess it has me more excited than recent versions. It’s not just for the technical improvements (which are many), but because PHP 8.5 introduces features that will change the way we write code.

And when I say “change,” I mean the kind of changes that, once you use them, you can’t go back. Like when the null coalescing operator (??) appeared in PHP 7, or arrow functions in PHP 7.4.

Mozilla AI surprises again: AI agents that work just by opening an HTML

A few days ago I came across a Mozilla AI project that really caught my attention: WebAssembly Agents. And after 30 years watching the industry complicate life with dependencies, installations, and configurations, seeing something that works just by “opening an HTML” made me smile.

The problem it solves (and we all know it)

How many times have you tried to test an AI project and encountered this?

After many years working with systems of all kinds, I’ve seen how information retrieval has evolved from simple databases to today’s sophisticated systems. But what Baidu researchers have just proposed has particularly caught my attention, and I believe it marks a before and after in how we think about intelligent information retrieval.

The problem we all know (but don’t always admit)

If you’ve worked with RAG (Retrieval-Augmented Generation) systems, you know they work quite well for direct questions. But when you face queries that require multiple reasoning steps, comparing information from multiple sources, or handling contradictory data… that’s where it gets complicated. And a lot.

The hype vs reality: reflections from a developer with 30 years of experience

This morning I came across a talk that made me reflect quite a bit about all this fuss surrounding AI and software development. The speaker, with a healthy dose of skepticism, does a “reality check” on all the grandiose claims we’re hearing everywhere.

The complete talk that inspired these reflections. It’s worth watching in full.

The Problem We All Have (But Solve Poorly)

As a DevOps Manager, I spend more time than I should configuring ways for the team to show their development work. Client demos, webhooks for testing, temporary APIs for integrations… we always need to expose localhost to the world.

Traditional options are a pain:

• ngrok: Works, but ugly URLs, limits on free plan, and every restart generates a new URL
• localtunnel: Unstable, URLs that expire, and often blocked by corporate firewalls
• SSH tunneling: Requires your own servers, manual configuration, and networking knowledge
• Manual Cloudflare Tunnels: Powerful but… God, the manual configuration is hellish

And then I discovered Moley.

Yet another protocol promising to change everything

When IBM Research announced the Agent Communication Protocol (ACP) as part of the BeeAI project, my first reaction was the usual one: “Oh, just another universal protocol”. With nearly 30 years in this field, I’ve seen too many “definitive standards” that ended up forgotten.

But there’s something different about ACP that made me pay attention: it doesn’t promise to solve all the world’s problems. It simply focuses on one very specific thing: making AI agents from different frameworks talk to each other. And it does it in a way that really makes sense.

The Problem We All Know (But Pretend Doesn’t Exist)

As someone who has managed web infrastructure for decades, I’ve seen too many bots pretending to be what they’re not. User-Agent: “Mozilla/5.0 (Windows NT 10.0; Win64; x64)” when in reality it’s a Chinese scraper sucking up your content at 3 in the morning.

Traditional methods for identifying legitimate bots have been, let’s be honest, pathetic:

• IP ranges: That change, are shared, or are spoofed
• User-Agent headers: That anyone can forge in one line of code
• Reverse DNS: That works until it doesn’t

Today Cloudflare announced that it’s integrating HTTP Message Signatures directly into its Verified Bots program. And after reading the technical details, I have to admit something: this could definitively change the rules of the game.

Confession of a converted skeptic

When Anthropic announced the Model Context Protocol (MCP) in November 2024, my first reaction was: “Ah, another protocol promising to solve all integration problems”. As a DevOps Manager who has seen dozens of “universal standards” born and die, I have reasons to be skeptical.

But after several months watching MCP be massively adopted - OpenAI integrated it in March 2025, Google DeepMind in April - I decided to investigate beyond the hype. And I have to admit something: I was wrong.