Cooked really good chicken this weekend
Any conversation
everytime i see projects like this, i think that a rss implementation it wolud be so cool. Although iknow that there is not that much rss lover out there haha
"If you don't think of yourself years ago as an idiot... Perhaps it is because you still are one."
In that spirit I started to write down my own thoughts. I think I am meant to call it a blog. Years from now I can read my old words and cringe at them.
www.gruntsoft.com/words/
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).
hรกt, jรณ, รฉppen telepรญtem a Windows 11-et, most jรกrok kรถrรผlbelรผl annรกl az รฉrdekes rรฉsznรฉl, hogy a TPM 2.0-รกs processzor-izรฉ egy Rufus nevลฑ programmal elvileg szoftveresen kivรกlthatรณ, meg hogy a windows 1125H iso-t kell beletรถlteni egy minimum 8 GB-os pendrive-ra
Well, I'm currently installing Windows 11, and I'm getting to the interesting part, where the TPM 2.0 processor chip can be replaced in software with a program called Rufus, and where the Windows 1125H ISO needs to be loaded onto a pendrive of at least 8 GB.
one more step. just a moment. attention required! enable javascript and cookies to continue. verifying the security of your connection. your browsing activity has been paused. content unavailable in your region. 429 too many requests. 403 forbidden. connection has timed out.
Itโs using the
/firehose endpoint. Itโs an SSE endpoint publishing everything latest. Though I meant it to be used server-side, since itโs heavily rate-limited โ up to 3 conns under the same network, but I canโt control how clients decide to use it so.. ยฏ\_(ใ)_/ยฏ