Loved this. It's funny how basic all of this can be. We have all these skills and and tricks and incantations whatever else, when it probably all just comes down to giving the agent the right info to set them up for success (just like you'd do with anyone you're delegating anything to).
Looks neat! I've been using Amp (https://ampcode.com/) for a while (Which seems to be doing something very similar), and I really appreciate this type of workflow. One thread = one VM feels like a solid model going forward.
Same instinct locally with git worktrees: one agent per worktree so they do not thrash the same checkout. Cloud VMs buy isolation and scale; worktrees buy cheap isolation when you already have a machine. I end up using both patterns depending on whether the bottleneck is compute or just not stepping on each other.
Agreed. Per-thread VMs are quite similar to how local agents use worktrees to avoid cross contamination, but with the added benefit of being able to easily scale up/down compute requirements on demand.
Hmm, it was a while back so now I'm struggling to recall, but I remember feeling like I'm going against the grain of easily using GitHub. I followed this exact tutorial at the time and it looks like there are now sections on how to work with GitHub.
Perhaps I need to force myself to commit for longer...
It can definitely handle virtual workspaces and global state (if I'm understanding what you mean). I have an Aerospace-like implementation here: https://github.com/mybuddymichael/Helm.spoon
It has several features from Aerospace, but Hammerspoon's window management performance is not nearly as good as Aerospace's (not surprising!).
Overall, I've found it easier to just fork Aerospace and add various extra features to it, so that's what I'm doing now.
I've been using Jujutsu (https://docs.jj-vcs.dev/latest/) exclusively for many months, but I've always been intrigued by what GitButler is doing on top of git.
Duolingo has been around for so long that I feel like there should be a wealth of case studies showing how folks have used it to actually learn new languages. I've yet to see one, personally. (But perhaps I'm not looking hard enough!)
I actually think jujutsu is _more_ ideal for the agentic era. It makes it so easy to explore directions, experiment, play, backtrack, move commits around, etc.
Sure, but it’s still couched in legal theory that seeks to legitimize it. That phrasing suggests the rules need to be changed to legitimize it, which tracks with my understanding but not the rhetoric.
I've been using Macs since Mac OS 9, and Snow Leopard was indeed very good. It remains my favorite version of Mac OS. I actually think it was Snow Leopard that started the rush of developers to Mac as _the_ platform to use.
People don't want animojis, and they don't want other trite new features that only seem to exist because Apple feels it needs to demo something new every year.
What they want is something that just works without annoyances, distractions, failures, or complications.
Give them that and they'll break down the doors trying to get their hands on it, because it's so far from how most tech works today.
Animojis really feel like peak corporate board asking, "What do the kids like these days?" and dumping that shit into the world. Honestly ... AVERAGE age of the Apple board is 68!! This is a company that's reached some sort of corporate red giant stage where it's influence is massive but it's ability to grow is over and it's only real purpose is to generate heavy metals and seed them throughout the rest of the universe after it's eventual explosive death.
Why would it be bad business for Apple? Their business model is based on selling a holistic ecosystem. They don’t have any need to chase new features and there steady stream of high margin hardware revenue is at stake.
