Skip to main content

30 posts shown

  1. A sandbox that teaches swamp, managed by swamp

    by @webframp

  2. A candid account of navigating the swamp extension ecosystem, from forking a libvirt plugin to stalled PRs. Why the path of least resistance keeps winning over collaboration.

    by @evrardjp

  3. Results of my first day in the swamp

    by @evrardjp

  4. AI sucks at following instructions. It tries, but ultimately, it lets you down. Like a hyped up kid on too much addy with 17 different distractions, lets just say it tends to drift a little from your

    by @keeb

  5. Killing n8n: Migrating 11 Automation Flows to Swamp in One Day - killing-n8n.md

    by @lint

  6. Curating my media library with swamp instead of letting it grow forever - curating-with-swamp.md

    by @lint

  7. What changes when your agent can observe reality instead of reading your notes about it

    by @webframp

  8. I tweeted a twelve-point spec for what an agent-native cloud actually needs to look like. Vercel volunteered. Cloudflare's engineers got to work. Here's the test.

    by @webframp

  9. Reading the Swampexample42.com

    Day two with Swamp: I climbed out of the mud and actually read the docs on swamp.club — and the framework for giving AI agents typed, versioned, deterministic memory turned out to be rather brilliant.

    by @alvagante

  10. Sequential pipelines assume humans waiting in sequence. Agents do not wait.

    by @webframp

  11. swamp extension quality checklist. GitHub Gist: instantly share code, notes, and snippets.

    by @webframp

  12. Agent state that follows you, then your team

    by @webframp

  13. High trust doesn't mean no guardrails. It means everyone understands the direction well enough to act independently within it. When you pair that with the right systems, every person on the team can…

    by @stack72

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

    by @stack72

  15. Safety in the Swampwww.linkedin.com

    I've been using Swamp (https://swamp.club) quite a bit at $job recently, and have been running into a pattern that I feel is useful enough to share.

    by @bixu

  16. How Larry Wall's virtues of a Perl programmer inspire me in this era of engineering

    by @adam

  17. Adaptive building blocks are how automation keeps up with AI development

    by @adam

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

    by @adam

  19. How teaching your Claw about Swamp can help avoid the lethal trifecta

    by @adam

  20. Engineering with AI Agents doesn't mean you get to skip the fundamentals

    by @adam

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

    by @adam

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

    by @magistr

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

    by @magistr

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

    by @magistr

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

    by @magistr

  26. Hands in the Swampexample42.com

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

    by @alvagante

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

    by @webframp

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

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

    by @stack72

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

    by @stack72