i dont think its all talk, these are smart people that have been in ai since the 2000s, and they raise good points. current incentive structures are very dangerous long term
Any conversation
they too have every incentive to exaggerate because they are selling safety and/or books on the topic. I don’t believe we won’t see it coming. Any issues that will manifest will be very visible and we’ll have plenty of time to mitigate their impact.
they could be making a lot more money by just working at ai firms i fear. the thing that got me worried the hacking incidents lately, huggingface etc.
if the capabilities consistently outspeed the development of safety measures, and if the private arms race logic continues, i dont think this is a good spot to be in long term
sometimes my devices will make noises that seem to go off for no reason. it really stresses me out though, I can't help but always think something is doing it and if it's not me, then what?
what kind of noises? drives spinning up/fans ramping up?
random beeps and a sound that seems like the notification but it just isn't. I don't know maybe I'm crazy
Would a CO monitor help here? I mean to err on the side of caution etc.
I don't believe I know what that is
It was a reference to this nypost.com/…/i-thought-a-stalker-…was-even-scarier/
Job I was hoping for gave me the "we found another applicant" treatment. I don't begrudge them for that, since I know I had a 'less than adequate initial coding interview. But still, it stings and sucks. Hopefully my other interviews yield better results...
A credit union wants to get their own data out of a vendor's online system. Vendor wants $160,000. I wrote a script with to download the data just as though a user would. It's going to run for about 6 weeks to download around 250k records and 70GB of images.
you could split to buckets like alphanumerically and parallelize it if you don't want to wait that long. Probably need to launch a few instances but still cheaper lol.
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).