"Sharing economy" once meant something. You'd Uber someone B→C when already driving A→B→C→D; you'd AirBNB your home when vacationing and stay at someone else's home who was doing the same. No driving just for Uber; no houses just for AirBNB. I fear this history will be forgotten.
Any conversation
Agree, it was once like that. But a very long time ago and for very short period of time. Then, capitalism did its tricks.
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).
morning doodle of Vulpes.
ibb.co/WN48DSt3
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to:The proverbial first post should have been “hello world”. :-P You are the first rustacean I come across!
replied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:LOL! Good point:)
Preparing for opening up an app I'm working on for a public beta. Main is a quiet app that helps you maintain the value of your home:
…
Yes the og is downloaded and re-served, to avoid leaking/tracking of client information. You need to edit and save to refetch, I did it for you now.
…
Is this true? Sometimes, AI allows for socratic thinking, this is, the conversation with the machine allows the thinker to go further as the AI thorws ideas to the conversation. Many times, the AI reasoning is not good enough, but like a friend that says a funny think that sparks an idea, the AI can help our brain to see other possible paths.
The AI doesn't need to be right to be helpful