every society gets the kind of criminals it deserves.
Any conversation
"Think of yourself as dead. You have lived your life. Now, take what's left and live it properly." - Marcus Aurelius
ive been rocking my thinkpad 460s since 2018 or so, but ive just recently yolo purchased a chunky t420 for 80€. I gotta say this is the best laptop ive ever used, keyboard/io is unmatched and it still runs super snappy on omarchy right now, even with only 4 gigs of ram :D AND this thing has a cd drive!
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.
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 forgot that I was at work and did my big sneeze, not the work sneeze. The one where a startled deer looks straight into the camera, which then zooms out to a flock of pigeons taking off, and a crow makes a warning noise.
Someone dropped something in the adjacent lab. I hope it wasn't my fault.