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.
Any conversation
Sunk cost fallacy is no longer applicable in the age of . Now you can do broad changes without second thought, u can always revert back, without incurring the cost of doing so, since itโs all done so quickly and effortlessly.
I think it will still apply, just perhaps to a lesser degree. Kind of related to I wrote recently (not to shamelessly plug my stuff ๐ซฃ)
okรฉ, megdumรกltatok, a hรฉten telepรญtem a kis virtuรกlis รกllatseregletem mellรฉ (webszerver, mechanikus 1. generรกciรณs robotkezdemรฉny, led kijelzล szalag) az elsล ai agent chatbotomat, egyelลre Virtualbox Ubuntu alรก
Okay, you've got me, this week I'm installing my first AI agent chatbot next to my little virtual animal herd (web server, mechanical 1st generation robot initiative, LED display strip), for now under Virtualbox Ubuntu
took me until now to learn described images with low-cost models > attaching images to high-cost model. silly me. output quality remains, cost lowers.
"Sharing economy" once meant something. You'd Uber someone BโC when already driving AโBโCโD; you'd AirBNB your home when vacationing and stay at someone else's home who was doing the same. No driving just for Uber; no houses just for AirBNB. I fear this history will be forgotten.
Agree, it was once like that. But a very long time ago and for very short period of time. Then, capitalism did its tricks.
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).