@thechelsukprofilefollowCurrently in remission from ME/CFS after 3+ years. Occasional software engineering leader, app developer, blogger, zwifter, and just being online.wrote:
Any conversation
a constant, existential pull
so old I couldn't tell you the end
or draw its shape
between kind acceptance
and striving, struggling, writhing, climbing
learning, growing, discontent
"do you feel this way, too, at endless war with longing itself?"
but the birds and trees and ants and wind
in their own marvelous design
don't reply
I can't figure out what's leaking on my '73 F250. Shows up slowly at the back of the oil pan. It's pretty clear because I've recently changed fluids and scrubbed the engine.
It was definitely brake fluid for a while after it was overfilled but that has evened out. The oil level is steady after when checking every 10 miles or so.
I think anyway... hard to know with these ๐ฌ
ooh maybe I revive and add this feature but instead of being able to modify everything it would be limited to adding features to the game/world. And itโs the perfect domain, a site thatโs been entirely mostly hallucinated.
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).
pรฉldรกul Telegram, Facebook, stb., de ilyen รผgynรถkรถkkel bรกrki talรกlkozhat naponta, egybลl felismerhetลk, meg is kell ลket szรฉpen jelรถlni, รฉs egyre bรฉnรกbbak a szรถvegรผk is, ahogy megfigyeltem, gondolom, attรณl fรผgg, ahogy promtoljรกk, vagy instruรกljรกk ลket, ha a gazdรกjuk kifogy az รถtletekbลl, a projekt hamar elfรกrad, a bot csak unalmas h#lyesรฉgekre kรฉpes egy idล utรกn
for example, Telegram, Facebook, etc., but anyone can encounter such agents every day, they are immediately recognizable, they need to be nicely labeled, and their text is getting lamer and lamer, as I have observed, I think it depends on how they are promoted or instructed, if their owner runs out of ideas, the project quickly gets tired, the bot is only capable of boring nonsense after a while