I recently made a 10 foot sailboat and took it on a fifty-mile adventure in the Salish Sea. I can still feel the way the wind pushed the boat over the water. I kept imagining the way that our progress was the sum of the vectors of wind, current, and gravity.
Any conversation
Reggel egy kicsit letรถrรถltem a kis Gemmรกnak a csatolt rรฉszeit a szรกmรญtรณgรฉprลl, mert mรกr kezdett elegem lenni a hลฑlyesรฉgeibลl, mire apรกm azt mondta, hogy "van egy hapsi az interneten", aki hรบsz รฉve ezzel foglalkozik nem tudom, ha nem tลฑnt volna fel, รฉn is ezt csinรกlom amรบgy.
This morning I was deleting a little of Gemma's attachments from the computer because I was starting to get tired of her antics, and then my dad said, "There's a guy on the internet" who's been doing this for twenty years, I don't know, if he hadn't noticed, I'd be doing the same thing anyway.
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).
de a tapasztalatok szerint a kezelลfelรผlet elfรกradรกsa elลbb-utรณbb magรกval hozza magรกnak a rendszernek az elfรกradรกsรกt, majd lassulรกsรกt, szerintem 1-2 รฉv mรบlva (amikor mรกr senki sem emlรฉkszik majd rรก), forradalmi รบjรญtรกskรฉnt visszahozzรกk a Windows 10 kezelลfelรผletรฉt Windows 12 nรฉven
but according to experience, the fatigue of the user interface will sooner or later lead to the fatigue and then the slowdown of the system itself. I think in 1-2 years (when no one will remember it anymore), they will bring back the Windows 10 user interface as a revolutionary innovation under the name Windows 12.
what are ya'lls favorite wikipedia page?
I myself is partial to the 'variations' entry for high fives
Catastrophic interference is also a favorite Wikipedia page and concept. The thing is, it doesnโt only happen to artificial neural networks, Iโve had it happen to me a few times. Especially with pin numbers, newer pins overwriting old ones and Iโm always scared when Iโm having hard time remembering something that this catastrophic interference applied and now the information is gone from my brain.