But it has proven quite the challenge to support old Linux distros. We have tried using nix to pin deps, but this easily leads to new issues: hardcoded RPATHs leaking into binaries, glibc compatibility issues, etc.

If we instead fork the build environment and use an old Ubuntu for building our Linux app, then my life gets harder, because now I have two targets for a whole lot of internal tooling that my team maintains, and that tooling needs to be deployed to both build environments. Again, its the same shit: glibc mismatches, missing/different shared libraries, etc. Just causing problems in a different place.

There is certainly some element of skill issue at play. But I wouldn't call it easy.

None, really. Prusa printers are good enough though. If you value freedom and privacy, its worth a few extra dollars.

Perfect, $1mil in salaries to spare the company $500k in spend :)

My version of this:

For my friends, everything; for my enemies, pull security in.

Yes, capturing more shareholder value is a virtue.

I'm not outraged (the intentions were probably good), but I also strongly disagree. Don't touch my config without my consent.

This is also a good thing. Even in supposedly developed parts of the world like San Francisco it can be difficult to find a PCP that is taking new patients.

[0]: https://www.ietf.org/archive/id/draft-michel-ssh3-00.html

I'm a bit skeptical of this approach, at least for building general purpose coding agents. If the agents were humans, it would be absolutely insane to assign such fine-grained responsibilities to multiple people and ask them to collaborate.