uberduper

The take home is that any shared resource is a potential communication channel between two willing participants. In this case it was CPU cache, presumably because openai didn't bother with basic vm security practices.

There's so many possibilities that this type of thing will never be solved by invisible (to the agent) boundaries. The sandbox is just another layer in w/e problem you've given it to solve.

Yes. This quake was pretty far from the locks tho.

I got ghosted by Apple after traveling to Cupertino to do some phone interviews from an Apple conf room. I'm pretty sure I've been blacklisted there for reasons unknown. Their recruiters reach out from time to time and after a couple messages back and forth, they too ghost. I've even been referred by friends which results in a conversation with a recruiter that ghosts me shortly after.

I'm pretty good at what I do and I'm not weird. All the conversations seemed to go well so I have no idea what happened.

I get about 20 minutes of work from my 5h limit with the $20 plan. It wouldn't bother me as much if codex would continue after the token bucket refills instead of waiting for me to show up and tell it to continue. I don't jump to the $100 plan because I would be in the exact same situation.

Gimme an rtx spark in the new framework 13 pro.

My take from working at a Big Corp is that individuals using coding agents can increase velocity substantially and produce good quality work, assuming they are proficient with the tools. But it falls apart quickly when you have a team trying to work together.

imo we either need to centralize the agent and and submit plan, spec, reference doc MRs rather than submitting code changes. Or develop SCM systems/workflows that incorporate plan/spec/reference/prompt metadata with code so intent can be factored into merges.

Nix isn't involved in my container images. I just take the dependencies and env vars from the flake and generate a dockerfile.

Guess I need to try out dockerTools. That looks really convenient. Thanks!

I do the same. Codex manages a per project flake.nix and uses `nix develop` for all testing. nix-direnv for my own convenience. I generally have it generate dockerfiles or other deployment assets at some point.

Codex is way better at nix than I am.

The distinction is scale. "AI Datacenters" are a new level of scale with new levels of power consumption and heat generation. Sure you could run regular compute and w/e in them but it's not practical to build these mega sites for regular compute. GPU Compute / AI workloads require network/interconnect bandwidth and latencies where distance matters so you're forced to solve problems you wouldn't otherwise have to. Those problems are mostly solved with money.

No. Agendas like, "I need to push my ideas for promotion credits."

I'm building the same stuff I've always built. Just faster and with less dependence on others. Not having to argue with devs that have their own agendas has been my biggest benefit from coding agents.

TBF this was the case prior to the firmware change. It wasn't a bait and switch. It just wasn't obvious to someone buying a printer they thought worked with open source slicers.

Did you install the network connector Orca slicer prompted you to download? It's a closed source blob that runs on your PC which I'm presuming you haven't air-gapped as well.

`initcall_blacklist` is a thing.