HN user

uberduper

601 karma

Three idiots in a trench coat.

Posts0
Comments257
View on HN
No posts found.

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.

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.

I did some work on an agent that was supposed to demonstrate a learning pipeline. I figured having it fix broken linux servers with some contrived failures would make for a good example if it getting stuck, having to get some assistance to progress, and then having a better capability for handling that class of failure in the future.

I couldn't come up with a single failure mode the agent with a gpt5.x model behind it couldn't one shot. I created socket overruns.. dangling file descriptors.. badly configured systemd units.. busted route tables.. "failed" volume mounts..

Had to start creating failures of internal services the models couldn't have been trained on and it was still hard to have scenarios it couldn't one shot.

Do people really want codex to have control over their computer and apps?

I'm still paranoid about keeping things securely sandboxed.

I don't know anything about this particular site, but I presume it's one of the new mega gpu sites.

I'm seeing many people in the comments with an early 2000's era concept of datacenters. The scale of these new sites is mind boggling. Take your idea of a typical datacenter building. Make it 4x bigger. Then put 4 of them together into a cluster. Then imagine 10 of those clusters at the site.

There's going to be continued support from local electricians, low voltage wiring vendors, various facilities service companies, HVAC, and now plumbers.. lots of plumbers. So many leaks. A site like this is going to have probably a few hundred full time people on site all the time in addition to the contracted folks.

CDDL is more permissive than gpl. It's not a violation of cddl to intermingle with code under a different license. GPL is the issue and it's the individual contributors to linux that _could_ sue.

There's no zfs grenade. It's CDDL, feel free to use it wherever you want. Oracle can't come after you for violating the gpl even if somehow using zfs on linux violates the gpl.

AWS loop a long while back wanted me to design a playlist system so my dumbass brain snapped to m3u files or w/e people were using back then and designed a system to host/share playlist files. The teenager (ok probably in their 20s) interviewing me seemed more and more confused as we went on but he never tried to redirect me to what he really intended.

This leads to authors having to re-explain their thinking in detail, covering points that they’d omitted for brevity or because they are obvious to those with a good understanding of the problem.

There's nothing wrong with this. Being able to explain your thinking in detail to someone that doesn't necessarily understand the problem is a pretty good exercise to make sure you yourself fully understand the problem _and your thinking._ Of course, this can't turn in to a lecture on basic things people should know or have looked up before commenting.