When I stopped having a job I completely lost interest of huge portion of things I used to have interest before. I could connect all of that to consumerism. And I haven't gained any of that interest back.
Any conversation
I like this guy I drew
ibb.co/vxRtMxQC
I though textlog was a gonner there. It was several hours with just a 502 response. Glad to see it's back!
@stagasprofilefollow
creative technologist
creator of textlog - Is there a way to get an atom version of the โfor-youโ feed? Iโm guessing this is complicated by needing to be authenticated.
creative technologist
creator of textlog - Is there a way to get an atom version of the โfor-youโ feed? Iโm guessing this is complicated by needing to be authenticated.@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:The abuse (in my opinion) of the auto-translate feature is super annoying. Thanks goodness for โblockโ.
Gave this evergarden colorscheme a shot after seeing it on lobsters today. Quite liking it.
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
This #tome about #Tcl/Tk has me re-evaluating my plans to move to the woods to be a carpenter hermit.
Now I want to move to the woods and be a programmer hermit.
kรฉsztetรฉst รฉrzek, hogy valami ilyesmivel (is) foglalkozzam, a kรณdolรกshoz egyelลre nincs agyam, de majd azt is szeretnรฉk, csak scripteket, semmi komoly programnyelv, de vรฉgรผlis a JavaScript is scriptnyelv
I feel the urge to do something like this, I don't have the brains for coding yet, but I would like to, just scripts, no serious programming languages, but after all, JavaScript is also a scripting language
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).