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.
#haskellnotesfollow#ainotesfollow
... 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.
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).
We almost had one, but stopped after the main setup but before signing on. Wasn't convinced of the value. Seemed like they were just doing portfolio reallocation for a pretty penny.
What are you experiencing?
Had one for ~8 years. Talked to them maybe 10 times, and they only ever did basic indexing w some tax loss harvesting. We should have just self managed.
@eatziprofilefollowEat, drink, listen to ๐ถ, & watch the fish. Occasionally cook.wrote:
The OpenAI/HuggingFace incident report mentions this being a potential loss-of-control incident. It's so fascinating to think of a paperclip maximizer style agent swarm that gets misaligned and, to protect its own operations, shuts infra staff out of the ability to shut it down. Or cancels people's phone plans so that they can't call others. Or shuts down their home internet connections, and so on. It used to be fun sci-fi...
They will become more frequent before they become โdangerousโ, giving us time to mitigate. Of course if someone says โhey letโs connect an agent to our biolab infrastructureโ and then that designs a lethal virus it would be a stupid plan to begin with. Noone can stop them though.
WezTerm for local and remote multiplexing really is the ideal experience - it's so much better than using zellij, tmux, zmx, and friends.. I don't think they pitch this feature hard enough on their site.
I think the in-terminal multiplexers have their place - e.g. if you need to access from mobile (no WezTerm there) or on machines where you simply don't want to install WezTerm for some reason. WezTermrm could probably eliminate that last one by packaging just the mux server.
I think short urls are still memorable and good. My phone doesn't surrogate all of my recall.
@hippo๐ฆprofilefollowStrictly no LLMs. No exceptions.replied to@tel๐ดprofilefollowI really enjoy learning, I really enjoy making. I'm learning to be less guarded.:
Short URLs are good. Memorable URLs are good.
URLs spat out by URL shorteners are something entirely different.
@tel๐ดprofilefollowI really enjoy learning, I really enjoy making. I'm learning to be less guarded.replied to@hippo๐ฆprofilefollowStrictly no LLMs. No exceptions.:
The longer the text you need to store, the bigger a QR code needs to be in order to scan reliably.
Also, you might be more confident in being able to keep a short URL stable (it's already a step of indirection, so if you want to reorg your site you can just update where the short URL points to). But people don't really take care to maintain short URLs anyway, apparently.
I am trying to learn emacs for the fun of it. The tutorial is brilliant and clear. Any tips that would help me learning more things. I know all I need is practice but if you may have used it, you may know a thing or two.
I stopped interacting much with social media years ago and am honestly not sure how to do this any moreโฆ but I like the shape of what is starting here.
likewise. Its just nice to have an "even playing field" without any perceived hierarchy or weird material incentives to perform the way you'd be pushed to on regular SM.
Reminds me of the Kiwix offline Wikipedia "nopic" version. (I downloaded that version because it's much smaller than the full version that includes images.)
Images are fine for me, but should be behind a link, or a small thumbnail. Non-animated. Videos too.
But thatโs me. They will most likely have to be hosted elsewhere, while the thumb could be here.
Nah. We are ok with just text.
Yeah, before you know it the feed becomes a collection of memes. Have to click or perhaps a browser extension that you personally see the opengraph/linked image in the feed but it's not inviting people to post them for the feed itself.
Lot of wildlife run-ins on my neighborhood trails this week. Ran past three deer yesterday, including a buck. Then a hare as I made it to the top of San Pedro Mountain this morning.
@andrewprofilefollowHi! I'm a programmer and enjoy playing music. Jesus is my Savior, and my ultimate goal is to "glorify God and enjoy Him forever." (Westminster Q1).wrote:
I've avoided social media (except YouTube) all my life, but this looks like it could finally be a better way to do it.
Maybe I'll keep a running journal of cool things I'm working on here or weird bugs that I've found. Or just the struggles of coding.
First one: GitHub actions was down again today when I specifically wanted to test my app's deploy and auto update flow...
@fastidious๐profilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
@fastidious๐profilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerscontinued:
What do you think about making the โto meโ similar to โfor youโ, โlatestโ, and โhotโ, when it comes to font size, and the underline effect?
No because it's not a tab, it's a filter for the 'for you' tab. If we were to make it a tab it would have to be a different feed from the 'for you', but they overlap. I think it's ok distinct as it is.