Finished watching Titanic with kids. One of the best movies ever.
Any conversation
Ordered JBL Charge 6, waiting for delivery today. Will mount into my bike and will listen to music while commuting 25km to the office. I'm a victim of marketing, seeing an ad, buying stuff.
Last year I wasn't feeling too good.
I turned forty, waited for surgery, and was hurt by my own colleagues. So I dealt with things. Maybe not so well, but to the best of my ability.
One of the consequences was that I got a bit heavy. My body changed, and I didn't feel like myself. It was a problem for future me. So now I am here with this little belly of mine. We're not enemies, but I decided it's time to part ways.
So I count calories. Maybe not so well, but to the best of my ability.
Introduced an MCP server this morning for the app I'm working on (getonmain.com), based on a user request. Curious to see how/if folks use it.
I remain ambiguous. This morning I used pi+gpt5.6 to create a color scheme based on evergarden.moe. It works, and I havenโt checked how well it stay true to the style used in vim-bundled schemas. Before I wouldnโt have done this, and now I can. But I donโt know if it is good. github.com/โฆ/evergarden.vim
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).