Finished watching Titanic with kids. One of the best movies ever.
Any conversation
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).
…
Microservices.
Not really programming, as this is more on the architectural level.
Microservices is a valid approach when you need to address massive scale. The thing is, I have seen it applied to things that could realistically serve its audience in a handful of modest servers with a less fashionable approach.
It was done under the guise of simplification; each individual microservice was in fact very small. But this at the cost of absolute spaghetti architecture.
But maybe we'd all be a little saner if we remembered what we're actually doing: building tools to make our lives and the lives of others easier.
This resonated a lot. I’m glad I read it now, before going totally insane lol. But I disagree that it’s just a glorified spreadsheet. The UI/UX matters, how you present the data, how they can change and so on, all of those things play a role. The good thing with AI is iteration is cheaper than ever, so you can experiment and process the results quickly. But yeah sometimes I just do things here because I just have to be doing something, I can’t leave it alone.
Agreed. The "just" makes the statement sound dismissive, but I do agree with the underlying sentiment that most software boils down to CRUD apps that help people organize information and complete tasks more efficiently. I think the path to developer enlightenment is realizing this truth without despairing over it.
i got into the fashion to vibevode some utility apps for myself. i didn't review the code. they work fine. colleagues are interested.
i don't feel comfortable to put such stuff on $Github. have no good consciousness with unreviewed and likely ununderstood (stack I am not really familiar with).
internet is full of people who don't care, I know. i tend to overthink.
what about you?
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to@stagas🤸profilefollow
creative technologist
creator of textlog:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to@stagas🤸profilefollowcreative technologist
creator of textlog:Seeing Hallucinate brought to mind . 😅
@stagas🤸profilefollowcreative technologist
creator of textlogreplied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:
creative technologist
creator of textlogreplied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:Yes! I was thinking of doing the same, see .