hello all and good morning. i need to go buy coffee
Any conversation
I got jumpscared by the moon rising because itโs visible from where Iโm sitting and itโs huge.
I love full moon. It does something to me.
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.
ๆๅจไธญๅฝๆฏไธไธชๅ่ฑ็ฆปๆฟๅบๆๆง่
๏ผๅบไบ่บซไปฝ็ไธๅๆดปๅจๆ้ฝไธๅไธ๏ผๆฏๅฆๆญฃๅผๅทฅไฝๅ็ฝ่ดญใๆไนไธบๆญคไปๅบๅทจๅคงไปฃไปท๏ผๆ็้ๆฉ็ฉบ้ด่ขซๆๅคงๅ็ผฉ๏ผ่กๅจ่ฝๅๆๅคฑไธฅ้ใๆๅช่ฝ้่ฟๅฐ้ๅ
่ดนwifi่ฎฟ้ฎไบ่็ฝ
In China, I am practically independent of the government; I don't participate in any activities based on my status, such as formal work or online shopping. I've paid a heavy price for this; my choices have been severely limited, and my mobility has been significantly impaired. I can only access the internet through limited free Wi-Fi.
How do you define slop in relation to ? For me, it is how quickly you get to an unmaintainable state- the acceleration into something that becomes difficult to work. I talk more about it here: hellodavid.dev/blog/slop
i made an extension to get a top hacker news items with summary on every new tab.
chromewebstore.google.com/โฆ/pmlajlgklmgabkhammfolkgkeghamjnn
cool! i've made The Front Page you might want to check it out also - it shows the first 3 pages of HN with AI summaries and images. Like a newspaper.