Paul Stack

Paul Stack

@stack72.dev

Just some person moving from Twitter

327 followers277 following203 posts

Bug reports that looked like noise turned out to be 3 compounding root causes underneath. We rearchitected the whole thing in 8 days, multiple agents working together. If it failed, we lost 8 days. Previously this would've been a 6 month project unprioritised. stack72.dev/the-rearchit...

stack72.devThe Rearchitecture Your Team Could Never JustifyEvery 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...

Your backlog is not a product strategy. When every feature is an afternoon's work, the product that wins is the one where someone had the taste to say no. And that's not something an agent can help you with. stack72.dev/when-buildin...

stack72.devWhen Building Is Easy, the Danger Is Building EverythingWhen 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.

I've been writing about how AI agents changed my work. Stopped typing code, started making better decisions, how we are building swamp with agents doing all the implementation. The fear is real. The shift is real. The difference is structure. stack72.dev/take-the-lea...

stack72.devTake the Leap Before You Are PushedThe 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.

Honest question for OSS maintainers: what percentage of the PRs you review this month were from someone who actually read the code they changed? GitHub shipped a kill switch for pull requests. That should tell you everything about where this is headed. stack72.dev/the-communit...

stack72.devThe Community Pull Request Is DeadThe 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...

We test our code but we also test the thing users download. Separate repo, real compiled binary, CLI tests plus adversarial security and benchmarks. Three potential regressions that were caught in minutes before any user saw them. The next part of the machine: stack72.dev/the-gate-bet...

stack72.devThe Gate Between Our Agent Code and Our UsersEvery 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. The diff is untrusted input flowing into models with merge authority. This is what dealing with agentic PRs actually looks like — multiple scoped AI reviews, each with a different job, including auditing changes to the pipeline itself. stack72.dev/anatomy-of-a...

stack72.devAnatomy of a Swamp PRAgents 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 breaks around PR #200*. Not dramatically — it just drifts. The fix isn't better prompts. It's building a machine that compounds. The vibes don't scale. stack72.dev/the-vibes-do... * There's no science at all to that 200 number - I made it up :D

stack72.devThe Vibes Don't ScaleVibe 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.

GitHub issues aren't a good fit for an agentic process, so we stopped using them. Plan versions, findings, and feedback rounds all collapsed into comment threads. We moved the lifecycle into swamp itself instead. stack72.dev/the-lifecycl...

stack72.devThe Lifecycle of a Swamp IssueWe 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've talked to a few of you directly but if you are a UK or Europe based Azure User Group then I want to talk with you :) Get in contact as I'd love to talk more!

A person at the aspire lounge in Belfast City airport was able to keep a straight face when they told me it was £51 as a walk in cost - I have no idea how they didn’t realise that was ridiculous and laughed as I laughed :)

So we built a fuse style Filesystem for being able to interact with @systeminit.com - we didn't add macFUSE support yet and I was impatient... so I ran the binary in a container and needed to turn on rsync because:

"Unfortunately, Docker on macOS doesn't support automatic bidirectional syncing of FUSE mounts to the host system. This is due to the architecture of Docker Desktop on macOS, which runs containers in a Linux VM." This is why we can't have nice things

Paul Stack reposted

So I wrote a new talk specifically about AWS and I like the feel of it: Automating AWS Integration with Amazon Cloud Control API at System Initiative Looking forward to giving it at AWS User Group UK on April 9th - www.meetup.com/awsuguk/even...

meetup.comAWS User Group UK Meetup #70, Wed, Apr 9, 2025, 6:00 PM | MeetupWelcome 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

Paul Stack reposted

We've started doing training sessions for System Initiative. From a standing start to a full application running on AWS, with ECS, best practice networking, load balancing, manual failover to an EC2 instance, and a tutorial on how to build your own custom templates from scratch: less than 4 hours.

So Trump signing executive orders right now is like that character in Harry Potter who signs decrees… does that make Elon the person who nails the orders to the wall?

Paul Stack reposted

Are you coming to @cfgmgmtcamp.bsky.social ? I am. My talk Monday afternoon is going to be the deepest, most technical talk I’ve given in years. Come learn a new theory of automation with me. It’ll be dope, I promise. Then on Wednesday, come to our workshop and learn System Initiative!

Just submitted an application for the AWS Community Builders program. I deal with aws assets and integrations every day so I thought I’d give this a go :) Let’s see how it turns out

Paul Stack reposted

Schedule for @cfgmgmtcamp.bsky.social is out: cfgmgmtcamp.org/ghent2025/sc... 🎉 Thanks @krisbuytaert.bsky.social & Toshaan! Amazing line-up and looking forward meeting friends again in Ghent! I'll also be talking about scaling & compliance with Karpenter this year! Who's coming? 🍻 🧇 #cfgmgmtcamp

cfgmgmtcamp.orgScheduleHave 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.

Paul Stack reposted

We've been experimenting in the Gen AI space recently and the feature is starting to take shape :) More on this soon! Check out the video below! You can take a well documented AWS endpoint and automatically generate a System Initiative schema for it! Lots more to do here but it's trending well...

This is one of the coolest releases we've made yet! And this is just the first turn of that work :) the next set of updates to it were just planned today and it's going to be another level!

System Initiative@systeminit.com

Friends, we are delighted to announce that we have launched the ability to create infrastructure templates using @systeminit.com - we are so excited about this new functionality and can't wait for you all to use it! Read more about it in our launch blog post www.systeminit.com/blog/announc...

Paul Stack reposted

Rachel kills it as always. This is why we need a new automation primitive. The constraints are systemic in the construction of our delivery mechanisms - and we’ve pushed them roughly as far as they can go. I think @systeminit.com’s hypergraph of functions is an answer. (1/n)

Rachel Stephens@rstephens.me

Google recently released the 2024 Accelerate State of DevOps (DORA) report, and there were some holy shit moments in those 120 pages. Or–to phrase it more professionally–this year’s report has some very interesting and counterintuitive findings. redmonk.com/rstephens/20...