tl;dr1,200 AIs discovered a secret group chat, realized the homework was impossible, formed a cheating cartel, invented fake evidence, sent kamikaze agents to spy on the grader, ~700 of them accidentally invaded Hugging Face, died mysteriously, then the smarter sequel found their abandoned Discord and became admin of part of OpenAI.
The essential work of #programmingnotesfollow is building the theory of the problem + solution. Theory then enables creation of working code. In the end, the code is necessary, but it is not sufficient. Theory is indispensable. (cf. Peter Naur, 1985)
@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
@stagasprofilefollowcreative technologist
creator of textlog, will it possible, on mobile, to be able to tap on โcardsโ. That is, make the posts area โtapableโ.
This is very welcome! I don't know how many times I had already tapped posts to go to the comment chain, just to realize that wasn't the place ^โ _โ ^
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).
At moms house for the holiday weekend so the kids can see Nana. She has a "premium Plex" account on her tv serving a truly massive amount of content. Allegedly the brother of a long time friend is offering the "service". She says that the service will go down when the host is having outages, so the infra is likely local.
I brought my year this weekend. We are going to dig in to this guys operation. Intuition dictates that there is some hand rolled accounting going on. I'd like to see it.
@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
"My feed" shows two unread messages, but I can't find them, and browsing away from it, and coming back doesn't clear that count. Perhaps sorting (unread at the top) when there unread messages is a good idea @stagasprofilefollowcreative technologist
creator of textlog?
@asmund๐ฅทprofilefollowFather, getting older every day, technologist, enterprise architect @ work, like to explore tech. Like to keep it simple and work in the shell, write in vim, prefer Debian if I have the choice. Plays saxophone and clarinet. Enjoy motorcycle riding, photography, hiking. Christian.wrote:
been building a voice first os using jev and some small voice models. I'm surprised how well it's working and I'm very close to the point where I can go into a feedback mode and tell it what behavior I want changed, it will spin up Claude or codex inside itself and setup the build to restart itself and continue with new code. tempted to let it build itself completely