Skip to main content

FEED

// WRITING FROM THE SWAMP · JUDGED BY THE GATOR //

23 posts shown

  1. Talking with Stephen O'Grady about AI and building the machine that builds the machine

    by adam
  2. How teaching your Claw about Swamp can help avoid the lethal trifecta

    by adam
  3. Engineering with AI Agents doesn't mean you get to skip the fundamentals

    by adam
  4. Building the machine that builds the machine, in order to learn what I believe about the future of my profession

    by adam
  5. Step-by-step guide: install Swamp from scratch, set up @magistr/jscad-cad extensions, configure the Claude Code skill, and generate 3D models from text descriptions.

  6. How we built a CAD generation pipeline using JSCAD, Swamp extension models, and Claude — from choosing the right CAD system, through 7 iterations of debugging a genie lamp with 6-view projections, to…

  7. Deploying Cozystack on a Talos Kubernetes cluster using Swamp extension models, with claude-code handling the execution while the author approves steps.

  8. A 10-hour technical post-mortem of attempting to virtualize macOS Tiger 10.4 on QEMU with OpenCore, managed by claude-code and Swamp on Unraid.

  9. Hands in the Swampexample42.com

    Example42 delivers Puppet training, consulting and development services. It provides consulting on automation and DevOps practices

  10. Your team's workflow and your agent's lifecycle want different things

  11. This week I'm talking with Adam Jacob, founder of System Initiative and creator of Swamp, about what happens when AI agents change the entire shape of software development. We discuss how he went…

    by adam
  12. 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…

  13. 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.

  14. 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.

  15. Five people, $3,000/month, zero lines written manually. GitHub just moved to per-token billing. The era of flat-rate pricing absorbing your agent's inefficiency is ending. Your agent isn't the…

  16. 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…

  17. Encoding judgment the agent lacks into AWS operations

  18. Mechanical friction is dissolving, but do not mistake easy for simple

  19. 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…

  20. 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,…

  21. 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,…

  22. 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…

  23. 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…

Page 5