schuettc

I wrote down my whole setup in one place: how I work, from a bare laptop to a shipped binary. Most of it is tools I built and run in the open, tied together into one way of working. https://www.subaud.io/the-subaud-setup/

The workflow is capture, plan, implement, review, ship. Nothing is reviewed by the thing that wrote it, so review runs on a different model. Everything lands through a pull request, and merging is what deploys, with no credentials on my machine.

I wrote down my whole setup in one place: how I work, from a bare laptop to a shipped binary. Most of it is tools I built and run in the open, tied together into one way of working. https://www.subaud.io/the-subaud-setup/

The harness is pi, which I now use for everything because I can extend it. I pick the model per task, defaulting to a strong one and dropping to cheaper ones for smaller work. And I can hold a tool at an exact version or let it track the latest, tool by tool.

I wrote down my whole setup in one place: how I work, from a bare laptop to a shipped binary. Most of it is tools I built and run in the open, tied together into one way of working. https://www.subaud.io/the-subaud-setup/

Have been working on this one for a bit and it's been working very well for me. muster.tools

I'll create a new session and tell the old session to start the next phase there but standby for any questions that the new session may have. This preserves the context that has been built up while still letting the work progress with a cleaner slate.

Have been working on this one for a bit and it's been working very well for me. muster.tools

One interesting thing that this has done has made the proces of handoff smoother and better. When an agent's context is starting to get full and Claude is complaining that it's a good place to finish, but there is still work to be done.

Have been working on this one for a bit and it's been working very well for me. muster.tools

I just published cdk-github-microvm-runners. It's a CDK construct that runs GitHub Actions jobs on AWS Lambda MicroVMs: one ephemeral single-use VM per job, in your own AWS account.

After building a GitHub app, you can trigger actions on AWS MicroVMs through the deployed control plane. A webhook lands on a Lambda, which checks scope and labels and enqueues. A launcher Lambda pulls the job, launches a MicroVM, and pushes the runner's JIT config into it.

www.subaud.io/tmux-workspa... I feel like I keep changing systems every few months now. It's always for a good reason. One of my favorite parts of what I've developed is that it's easy to switch. Load it up in my dotfiles and pull it down to other machines and I'm ready to go.

In this case, I switched from cmux to ghostty + tmux. There were some things I really liked about cmux but I was getting some strange issues with long running sessions creating lag. Since switching, things have been better.

github.com/schuettc/now... Finally ready! This has been something I've been working on for a few weeks now and I'm finally ready to release. Not perfect yet, but looking very good IMO.

This is fairly specific to my setup - Record Player + Sonos. If you have something else, there's enough code in here that you could probably port it, but it does use that Sonos for important info.

github.com/schuettc/now... Finally ready! This has been something I've been working on for a few weeks now and I'm finally ready to release. Not perfect yet, but looking very good IMO.

Last night was They Might Be Giants.

Trail of Dead.

Last night was They Might Be Giants.

Tonight is Failure. Who apparently doesn’t go on until 10:45….

www.subaud.io/claude-code-... I love when a throwaway line from Claude turns in to an experiment that is both surprising and confirms my suspicions. I have a few interns I'm working with and wanted to plan out a sprint but Claude kept rushing me through the process because we had a deadline.