William Collins

For a long time, my definition of a successful software release was pretty simple: the tests passed, the binaries built, and the checksums matched.

I’ve written many nearly identical Python Dockerfiles.

On July 28th, the MCP maintainers shipped the 2026-07-28 revision.

The discourse on platform engineering Twitter and Reddit has been pretty consistent for months now: Terraform is dead, HCL is dead, the entire Infrastructure as Code stack is about to get vaporized by autonomous agents that translate intent directly into…

Open up the claude_desktop_config.json or mcp.json of the average AI tinkerer right now and tell me you don’t flinch.

Here’s a question I got asked recently: If a skill can already call a REST API using Bash, why bother with MCP?

Let me paint you a picture.

If you’ve spent any time building with MCP servers, you know the drill.

As AI dominates tech headlines and corporate strategies in 2024, an important distinction is being blurred - the difference between developing AI versus consuming AI services.

The foundation of high-performance computing that powers artificial intelligence lies not just in powerful GPUs, but in the intricate web of connections between them.

In my previous blog on Dilution of Ownership, I explored how startup funding rounds impact equity.

There is a lot of confusion surrounding the dilution of ownership, especially in the tech startup space.

Sometimes, especially if you aren’t a developer by trade, you can get stuck on something small that will find you banging your forehead on your desk (figuratively, of course).

For many moons, importing existing infrastructure (that is to say, infrastructure running outside of Terraform state), has not been a trivial task.

What fits somewhere in between re:Invent and Community Day events?

I recently wrote a blog about generating Terraform with ChatGPT.

Usually, when it comes to technology, my grandmother doesn’t know much because she doesn’t care.

In Part 1, we talked about the origins of the Site-to-Site VPN Service in AWS.

At the end of each year, I take some time for self-reflection.

As far as tech conferences are concerned, it’s hard to find one as exciting as AWS re:Invent.

The necessity for protocols to keep communication secure has been around since the dawn of the internet.

Blowing out cloud spend is an easy thing to do.

Optional attributes for object type constraints is almost here!

There is a reason why enterprises prefer the best-of-breed approach to connect and secure their network and intellectual property.

I had the opportunity to present at the 4th annual AWS Community Day for the Midwest in June.

Zero Trust is all the rage lately, and traditional VPNs are getting a lot of scrutiny since they essentially add and remove encryption at the firewall.

Anyone that has worked in tech knows that building greenfield is much easier than dragging along brownfield environments through a roller-coaster they aren’t ready for.

The year is 2022, and Kubernetes is wreaking havoc on software delivery as we know it.

The public cloud continued to dominate spending in 2021.

New to cryptocurrency?

In Part 1, we laid out our foundation.

Check out Part 1 and Part 2 where we put together a scalable foundation and connect cloud networks from AWS, Azure, and GCP.