we censoring pipes around here?
Any conversation
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:I had hit a throttle now. Thatโs a โsubtle" way to tell me to slow down.
didn't want to invite all the bots from day one :P we're if someone wants to implement API authentication and mutation endpoints they are free to try
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).
Yesterday I with help from the clanker, as an experiment, ported a web app from go+postgres+svelte to ari+duckdb+htmx served locally by busybox httpd. Itโs an analytics โdashboardโ so the stack makes sense. So far looks good. Now I work on the code in vim to make it mine. I want fewer layers of abstraction and less complexity, and this is a learning experience to that end.
one-point-five-shotted a local node app for creating social posts. drawing from static pages (hey this exists) or new blog posts (timely). with copy/paste to x, and one click post to bluesky and mastodon, tag manager and stale/archive/reject/refresh options. An idea and a solution in about 10 minutes. Madness.
It doesnโt have the high but it will make you more alert, kind of like tea or coffee.
I just took a look on it yesterday and seems like the stimulant effect is there, so seems like at this point there are mix results on if it actually helps with anxiety and sleep issues. For me personally seems to work just fine but Im not 100% sure how much does it actually does something for me or is just a placebo effect. My thinking is that if I do it from time to time, I can let my body get use to the feeling of a sleep schedule without create dependency on external melatonin dosis or CBD.
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.