Yeah, my buddy had a real bad one with a semicolon in C. He was pulling his hair out for a full weekend because his loop kept exiting early. Turned out he had typed a semicolon right after the for statement, which basically made it do nothing. The worst part was he'd shown the code to a couple people and they missed it too. It's always the tiny things you stop seeing after staring too long.

Buddy of mine cheaped out on a condenser line last year. Thing blew a seam during a pressure spike and flooded his mechanical room. Sometimes that extra cost up front is just cheap insurance.

Hard way is right. Thing is, @logan648, most people miss the part where it keeps happening even after you learn. You patch one leak and another one springs. It's not a one time lesson. It's a whole process of constantly watching for new cracks. Gets exhausting, but that's the real takeaway.

Oh MAN, 4140? You ran 4140 at full feed on a brand new setup? That's the part that gets me! That stuff can be so nasty if it work hardens even a little. Dave was trying to save you the headache, those first piece jitters are real.

Remember my old robot vacuum that kept ordering weird stuff online. Turns out it was on the main network and got messed with. I just unplugged the thing and went back to a broom.