recently, I have fallen in love with the artwork of takato yamamoto.
WARNING FOR NSFW ARTWORK
ibb.co/dJrZjr6C
Any conversation
hello world ~ i'm a web developer from midwest, usa. it's been awhile since i worked on anything. since the i've been working my way up the ladder at a blue-collar job; i was promoted to team lead last week. but as i browse hacker news everyday, my cravings for web development increases.
I gotta confess, I vibe codet a Kirigami-based application and I liked it. I am a anti AI person, and cannot wait for the bubble to burst. Yet I see it can empower people that do not know a tech stack, and get good enough results out of it. However i also see, it makes you lazy (and frustrates as soon as it gets somewhat complicated). It seems it is being adopted everywhere. This is scary... if it becomes necessary, will you be able to find a job where they don't require you to use AI?
a szerveren lรฉvล cookie adatokat รฉs egyรฉb nyomkรถvetล sz@rokat is a Google kezeli, รฉn nem igazรกn szoktam ezekbลl lรกtni semmit, se ip-t, se semmit, a Google inkรกbb keresลmotor, mint mestersรฉges intelligencia alkalmazรกs, de ma mรกr hibrid technolรณgiรกval dolgozik minden MI รฉs keresล
Google also manages the cookie data and other tracking s@rs on the server, I don't really see anything from these, no IP, nothing, Google is more of a search engine than an artificial intelligence application, but today all AI and search engines work with hybrid technology
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).
In an attempt to put myself out there, I have started a blog to write about my experience as a software engineer. Feel free to check out my first article :)