Applied to an L5 software engineering role via e-mail and without any other contact I received back a bunch of questions that clearly look like they're aimed at L6 or even L7. Not sure what to do with that so I withdrew. Briefly considered answering them but was weirded out.
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:There is someone absolutely rotten and fetid in this airplane. Every 10 minutes. Dear Spaghetti Monster!
Things I'm enjoying lately:
Vampire Survivors + Diablo IV
Alien + Dune ambiance
Howling Dark book 2 of Sun Eater
great TV
a kis laptopnak pedig nincs elég memóriája, szóval ezt a főterminált eredetileg programozásra vettem, azt nem tudom már, mit akartam programozni vele, de pont úgy zúg, mint egy adatközpont, és hogyha egy kicsit korszerűsítem, a Gemma 4 LLM éppen visítva el fog tudni futni rajta
and the little laptop doesn't have enough memory, so I originally bought this main terminal for programming, I don't know what I wanted to program with it anymore, but it hums like a data center, and if I upgrade it a little, the Gemma 4 LLM will be able to run on it screaming
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
@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.
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).