Enjoyed reading โrevo, the programming languageโ post:
Any conversation
I've been on a kick lately of trying to visualize the oscillating clock, and ultimately the effectively arbitrarily complex activity of a computer processor, as modern refinements of the line shaft factory of the 19th century. Of compute as being not much more than profoundly refined "work" delivered by the electrical grid into marvelously complex machines.
Does that, as a metaphor at least, feel as important to you as it has to me of late? We spend so much time in a world abstracted.
bill gates built microsoft by making computation cheaper faster and harder for government to restrain. now that he's a billionaire no longer dependent on the free market for his own success he's discovered the virtues of taxing the next wave of computation. 1995 gates would have called it a tax on innovation. classic pull-the-ladder-up-behind-you politics.
setting up some of my workflows based on this writeup - ludwigabap.com/โฆ/on-my-personal-โฆof-the-tools-i-use/
Particularly a big fan of zellij amongst others
Also venturing into having agents enable more of my work - let us see how that goes.
"Think of yourself as dead. You have lived your life. Now, take what's left and live it properly." - Marcus Aurelius
I surprised my self this morning. I was looking for some content on YouTube with Mario (pi) and saw something that was 2 months old. First reaction was โthat is too old.โ I used to take my time, slow it down and have time for thoughts. Is this whatโs happen to you when consume too much?
@kapankatsuragiprofilefollow
I may know more about Disney History and trivia than you. Maybe, I dunno.
I write about pop culture on Super Review Time.replied to:
I may know more about Disney History and trivia than you. Maybe, I dunno.
I write about pop culture on Super Review Time.replied to:yes. everything goes so fast nowadays that we don't stop to appreciate stuff that happened the last month, two months, a year, 5 years ago.
Ikea has rules for naming products (so in theory, you could figure out what it is from the name) -> www.ikea.com/โฆ/6f564c4d-2ccc-46de-โฆ545a3948dc79.html
Things I'm enjoying lately:
Vampire Survivors + Diablo IV
Alien + Dune ambiance
Howling Dark book 2 of Sun Eater
great TV
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).
