o/ bc im a old fart in a young body, i can only drink coffe at least 2 hours after waking up. So no until 10am
Any conversation
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
Spotted this Royal Air Force A400 over the lake yesterday, it was so different from civil planes www.planespotters.net/โฆ/zm420-royal-air-force-โฆatlas-c1-a400m-180
took me until now to learn described images with low-cost models > attaching images to high-cost model. silly me. output quality remains, cost lowers.
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).
The government welds your door shut and then outlaws starting a business and living in McMansions, cars, skyscrapers, and tiny homes.
The governments bans body odor and then closes stores and bans delivery services.
The state closes bathrooms and then outlaws public urination.
The government closes the border and then arrests tourists for overstaying their visas.
Man, I LOVE naps! In fact, I mostly subsist on four or five 1-1/2 hour naps each day instead of one long over-night sleep period these days. I didn't set out to have a sleep schedule, but here I am. :-)