Hi, I'm Den 👋

This blog post is part of a series on exploring the Halo game API.

This blog post is part of a series on exploring the Halo game API.

For the past year, Model Context Protocol (MCP) has done a lot of maturing - starting as a small open source experiment, it now became a full-fledged protocol that is broadly adopted by the industry at large.

As an open source project maintainer, one of the things that I often need to do, to the surprise of no one, is triage issues.

Just a few days ago I wrote about wrapping up my latest Microsoft chapter.

Three years and a quarter ago, my hiring manager asked me - “How do I know you’re not going to leave Microsoft again if we hire you?”

Well, well, well - as 2025 draws to a close, I thought I’d resurrect an old trend and start writing yearly summaries again.

This year I wanted to be a bit more intentional with spending time reading.

This blog post is part of a series on exploring the Halo game API.

Hard to imagine that just a year ago we had so much work being thrown into Large Language Models (LLMs) but not a single protocol that would enable them to do things like tool calling.

We’re less than twenty four hours away from the new MCP specification dropping - it will mark the first anniversary of the protocol.

This blog post is part of a 📸 photography series on this website.

Just this past Friday we put the current Model Context Protocol specification in “frozen” state.

I’ll start off by saying that I am not at all an AI doomer - by any stretch.

I get to finally write a bit about a project I was knee-deep in for the past month - GitHub Spec Kit.

One of the interesting things about the Model Context Protocol (or, MCP as you might know it) contributor community is just how tight-knit it is.

No.

If you’ve been following the development of the Model Context Protocol (MCP), along with my post on old security rakes in new MCP yards, you’ll appreciate this latest security enhancement in Visual Studio Code.

Authorization: the part of your project that’s always more complicated than you expect, and never quite as interesting as the thing you actually want to build.

Every developer knows this frustration: you’re working with an AI agent, and it diligently works on generating code that’s almost right, except it assumes you’re using PostgreSQL when you’re actually using MongoDB, or it creates a REST endpoint when you n…