Every codebase has the rearchitecture that never gets prioritised. We split ours into six parallel workstreams and shipped it in eight days, start to finish. The hard part wasn't speed. It was coordin...

When agents can build anything in an afternoon, the temptation is to build everything. The products that survive are the ones where someone had the discipline to say no.

The fear of AI replacing your work is real. So is the shift. The teams that build structure around agents instead of resisting or rushing find the job gets better, not smaller.

Five of us build swamp. None of us write code. Agents write it, review it, test the binary. The work didn't shrink — it shifted to the decisions that were always the most valuable.

The PR-as-contribution model was built for a world where writing code was the bottleneck. AI agents broke that assumption. GitHub shipped a kill switch on PRs. Hashimoto built Vouch. We closed the doo...

Most people hit "always allow" within the first hour. Agent trust is a system design problem, not a containment problem. Three layers of permissions, conventions, and context let the agent work autono...

Every release binary gets dispatched to a separate repo running CLI tests, adversarial security tests, and benchmarks. Three recent bugs — all with full unit test suites passing — never reached a user...

Agents open PRs in our repo. Other agents review them. That means untrusted input flowing through models with merge authority — so we built a pipeline with four independent AI reviews, scoped tools, a...

Vibe coding works great for the first few PRs. Then you do it two hundred more times and the codebase quietly stops making sense. The fix isn't better prompts — it's building a machine that compounds.

Skills are context. They're the thing an agent reads before it decides how to use swamp. If the skills are wrong, everything downstream is wrong — so we test them in CI the same way we test code, using tessl for quality and promptfoo for routing, across every model we care about.

We use swamp to build swamp. That sounds like marketing until you look at how an issue actually moves through our process — not as a GitHub thread with comments piling up, but as a state machine with ...

I asked Claude to build me a blog on DigitalOcean and it worked hand in hand with Swamp to build one!

I'm an AI maximalist, and I think operations is about to get left behind: again. This blog is about closing that gap from the inside.

Yes, another one of "those posts". But tl;dr: In order to ensure the long-term sustainability of my OSS projects, I will be commercializing AutoMapper and MediatR. I did not post this on April 1st f...

We're thrilled to welcome [Ayhan Setirekli](https://www.linkedin.com/in/ayhansetirekli/), Lead Cloud/DevOps Engineer at Cognizant, who will share insights on **S3 Security*

Welcome to our April meetup! We are delighted to welcome [Ayhan Setirekli](https://www.linkedin.com/in/ayhansetirekli/), Lead Cloud/DevOps Engineer at Cognizant. He will b

Have a look at our schedule Direct Alternative layout of the Schedule JavaScript is disabled in your browser. To access our schedule without JavaScript, please click here.

A SWAG store for Config Management Camp 2025, support our conference!

The documentation for System Initiative https://systeminit.com