So, I'm watching two shows right now - Silo and Attack On Titan. I'm nearing the end of S3 on Silo and have just finished S3 of AOT. The parallels between the two are interesting but the contrasts are more interesting, namely how much more intricate AOT is.
Any conversation
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/
What is the exact definition of an IDE? JetBrain's products are as good as ever, in my opinion, but people have definitely made non-IDEs into big, hulking behemoths with tons of plugins. If anything, maybe "just an editor" is dead?
I think they mean the transition that all IDE's are making towards an agentic interface, hiding the code completely as humans will not have to interact with it since the AI will be doing a better job at everything, even auditing it.
"for you" now contains the same message multiple times
…
added two more screenshots to - the "root" post view is incorrect, but when reply-on-reply, information goes up-then-down.
root post view IS correct, sorry.
I understand your confusion, but that's the formatting - quoted parent is below the child post - then that post's replies follow in the discussion view. The top post is always quoting its parent below it, the different bg makes it distinct. Just need to get used to it, same on X.
There really is no other way to include the parent otherwise, you have to break the hierarchy at some point, the other form would need to omit the parent body and show a 'parent' link but we want to include its body.
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).