Laying in bed isn't the same as resting, and it sucks.
Any conversation
This #tome about #Tcl/Tk has me re-evaluating my plans to move to the woods to be a carpenter hermit.
Now I want to move to the woods and be a programmer hermit.
bill gates built microsoft by making computation cheaper faster and harder for government to restrain. now that he's a billionaire no longer dependent on the free market for his own success he's discovered the virtues of taxing the next wave of computation. 1995 gates would have called it a tax on innovation. classic pull-the-ladder-up-behind-you politics.
I've linked up my blog (jeff-mitchell.dev) to
textlog. I hope to use the two things together now to build a bit more of a writing habit. The 500 character increase is nice, room to breath but not an essay. Gotta build the muscles slowly :)Ubuntu telepรญtรฉse a VirtualBoxba rendben megtรถrtรฉnt. Mรกr csak egy รผgynรถkรถt kell bele fogni, รฉs mรกris kรฉsz az "AI torture chamber", ahogy a Futurism รญrja... Mondjuk, elsล kรถrben mรฉg nem รญgy fogalmaznรฉk...
Ubuntu has been successfully installed in VirtualBox. All you need to do is add an agent and you have an "AI torture chamber", as Futurism describes it... Let's just say I wouldn't put it that way at first...
Really glad to be using Haskell for work - especially in today's climate with agentic coding.
Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself.
We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker.
... because letting the agent run docker gives them a too-easy escape hatch from their sandbox.
So we're currently stuck with using VMs. This turns out to be tricky but seems do-able.
My current approach is to provision a VM image and use Incus for the execution. My main goal is to keep my current workflow of local/non-agent dev working seamlessly and share the source with the VM/agent.
This means sharing my working dirs with the agent VM but overlaying artifact dirs from VM-owned block devices so we don't take too big of an IO perf hit.
I also don't want the agent to be able to
git push so that means we need some quirky git config to rewrite origin paths and thread through some agent specific PATs ("thanks" GitHub) for read-only repo access. These ALSO need to be threaded through to the development containers - they need to clone private repos.... in the end, this seems to work but I haven't lived with it for long.
There are still some quality of life issues to work out, but I think it'll work out.
At this point, I've removed all coding agents from my host - and that's nice.
Curious, why does using Haskell make a difference here?
It's tangential to the sandboxing topic, really. I started the first post with a broader intent in mind and then elaborated on the sandboxing setup I'm working on.
For AI-assisted coding, though, it's nice because Haskell provides a lot of feedback earlier in the development process compared to lots of other languages. It tends to work once it compiles (obviously not all the time).
I though textlog was a gonner there. It was several hours with just a 502 response. Glad to see it's back!