
People have built some sick slack bots with Swamp, and now it's even easier: youtube.com/watch?v=U34klx11…

Infra Coder with a militant interest in DevOps and Systems Thinking. Speaks with a funny accent. **Evangelist of Life**. DAF

People have built some sick slack bots with Swamp, and now it's even easier: youtube.com/watch?v=U34klx11…


if you truely want to build a factory start with the basics: - capture all agent traces - measure time to merge - measure token spend > merge - measure ideation to merge - measure incidents - measure human productivity a factory is just above applied ps. lights off isn’t a thing yet. skilled humans needed to whip an agent in /planning mode

If you are a Senior+ engineer today and you still strongly believe you can outperform agents delivering reliable and safe code. I have some really bad news for you.

Applications are now open for the Anthropic Residency, a paid, fixed-term research program for academics, technical founders, and staff-level engineers who want to make AI safe and beneficial for everyone. No ML background is required. Apply by November 22: alignment.anthropic.com/2026…


Ok, tried out Rex by @mitchellh and @superlogical - it's fast and smooth - for a beta this is very good quality!

San Francisco traffic is crazy - 95 minutes to go across the bridge into the city and I’m not even at my destination…,

What’s up GitHub universe! Come hear me talk at 10! Say hello! We’re talking about not reading the code anymore, in choose your own adventure style. Two presenters, neither have read each others slides. It’ll be the funnest talk at the show.

Last week @nickstinemates took me from a fresh Swamp install to a 4am cron job that triages the neglected issues on the Rawkode Academy GitHub. The agent works it out once, writes a TypeScript extension, and from then on it's just a tool call. Same result every run. Full session: rawkode.academy/watch/hands-…

Brutal truth from @Lethain “If you're in [middle] management (…) you sort of have to decide, am I retiring now or am I re-skilling?” He did just this: step down from leading a large team (250 ppl) to be hands-on with a small team (25 ppl), ship code & re-learn the new “rules”
Why a 3x CTO went back to a 25-person team. From Will Larson @lethain, Imprint CTO and 4x book author. "It's a hard time in middle management, right? There's a lot more competition for these roles. What I found personally very rewarding is getting back into the details of writing software. When I left Carta, my team was around 250. When I joined Imprint, the team I was leading was 25. This a unique moment to actually re-skill. If you're in management, I think right now either you have to get back into the details, or the world is changing so radically that the profession you know will not be valued in three years. You sort of have to decide, am I retiring now or am I re-skilling? I think there has to be some openness to taking a backward step or a lateral step. What I knew I wanted was getting back into the details and relearning how to do software in the current age. That's what I believe is going to be the unlock to the longevity of my career."

Scanning and patching CVEs is, as everyone knows today, a real pain. Here's @sfalcon showing you how to do security scanning for the PHP vulnerability with Swamp: youtube.com/watch?v=NuxZGEYo…

Waiting patiently for @deno_land to sort the merge conflict out for Deno 2.9.8 so that we can roll out the fixes for the eMudhra cert authority

I am thrilled to tell you that Swamp Club has raised $7m in seed funding from @AmplifyPartners, Encoded Ventures, @jesserobbins, and @stolinski. Swamp is a platform for building AI systems from repeatable behaviors, rather than from token-hungry agent-centric designs. More exciting to me than the money (which I'm stoked about,) or the product itself (which continues to surprise and delight me every day,) is the incredible group of people who have started solving real, practical, everyday problems with Swamp. They teach me new and exciting things about how to build with AI every day. I'm grateful to my co-founders, who have poured every ounce of their creativity, passion, and intelligence into Swamp. I'm grateful to our users and customers (big and small) - there is no greater gift you can give to an entrepreneur than the validation that comes with voting with your wallets. And I'm grateful to our investors, who see the opportunity we see, and want to make it happen with us. It's such a cliche to say that there has never been a better time to build - but really, it feels like there has never been a better time to build. Come join the Club. swamp-club.com/press/swamp-u…

We're throwing a little meetup and getting together to talk about Swamp / the cool things people are building with Swamp in San Francisco on October 28th. swamp-club.com/meetup Come meet the team, listen to some talks, talk with other community members, and eat some good food.

Here’s the truth about where the industry is at with AI adoption: most of it is awful, and most of us are suffering under the weight of it. Early on, the bet was that the models are really smart and we will just chuck everything at them and let it sort it all out. This has largely led to incredibly wasteful, in-reproducible solutions - like huge skills and MCP, where the agent re-solves your problem a million times, getting it right some percentage often. Turns out it’s hard to get that to produce real value beyond individual experiences. As engineers, we have struggled to get our heads around how to use these capabilities effectively. Is it the harness? An agent? A factory? A tool call? Maybe a skill? How about a dark factory! We need RAG! No, RAG sucks, we need… you get my point. Everyone needs to take a breath, and start thinking about this new capability as a component of your systems, rather than the substrate upon which your systems get rebuilt. Meanwhile, coding agents got fucking fantastic. But for most of us, we changed nothing about our SDLC except that now we should be doing it all faster, because agents. That leads us to be stuck like a surfer in the chop - being responsible for everything but in control of nothing, with an avalanche of code nobody looked at when they wrote it, but that you’re responsible for ensuring doesn’t break the world. Luckily, we can stop the madness spiral. Breathe. We can engineer our way out of this problem. Are you working on how to use AI to improve your SDLC? If so, start by looking at how it works now, and using AI to automate it. Where in the process do you need intelligence? Is it there. How much do you need? Use that to decide your model. Encode the standards. Swamp, and primitives like it, are a part of how you do that. They solve problems like how to break the problem down into reusable components, how to store data, how to build the contract between components, how to string them into workflows, and how to expose that to agents, ui, or whatever you want. The way out of the suffering is to turn our engineering brains back on, and start building in ways that enable and support the future.