90%+ of production issues are caused by developers believing production machines are magic and have unlimited resources so can handle any shit code they write

Not in my experience. I would say it's more 50/50.

50% of the time it's my shit code.

The other 50% it's the network or operations teams playing "fuck around and find out".

@sariel oh yes that too... And can understand what you mean vs what you explicitly tell em to do.... That's part of the magic

Haven't had issues with network guys

Most of the production issues I encounter comes from misdesigned hardware that requires workarounds in software. Sometimes even multiple rounds because one workaround uncovers another misdesign.

@Fast-Nop you design chips? Or like like level code?

I'm basically Java and JS...

@donuts Not chip level design, that's off the shelf, but custom hardware design. I don't do that, but I need to read the schematics and specs to figure out what to do.

However, the fallout of hardware misdesign is on me because it's a lot cheaper to update the software than to recall and modify all the delivered units.

@Fast-Nop ain't that the fuckin truth.

That seems to be how most iis deploys work lol

I have definitely needed to have the "your disk is finite and your log files are not" conversation with a dev before. After the third time they crashed a prod server due to running out of disk space.

@EmberQuill yes but everyone else on my team graduated with CS majors... This is like How Computers Work 101...

@donuts to be fair, everything I build runs in the cloud, and for some reason even some people with CS degrees see "the cloud" as an infinite world of endless possibilities rather than "literally just servers in someone else's data center."

@EmberQuill I guess they don't see or pay the bills