I was curious of testing the Omarchy distribution this week just because I had some free time to work on it. I saw a lot of hate around it and kind of get the point but so far at least for what I have been doing it wasn't terrible (at least at the point of writing this) although I am not trying to convince anybody to use it. But it just remember me how much do I hate MS.
Any conversation
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
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.
My friend won 2nd place in the pc demo competition at Evoke in Köln this weekend, with his ascii-inspired demo Glyphnosis. Really happy for him! 💥
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).
anything you'd like to talk about
Interface looks sleek. The idea of text based messaging is quite interesting in the age photos and videos based heavy apps.
haha, yes. it's quiet on here though!
That’s also the point isn’t it? The people who like this place doesn’t like it too busy. So for them (us?) it will be a nice place to hang out as long as it stay uncommercial and low-key. But to be prosperous and interesting to the creator, it need to grow. 🤷♂️