4 ms·

Thanks. I really like idea number 2. In training, have people fail nearly purposefully. I think some of the problem is that there's no real standardized trai

by axaxs 5y ago

Thanks. I really like idea number 2. In training, have people fail nearly purposefully. I think some of the problem is that there's no real standardized training for developers. Many have 4 weeks of 'bootcamp' and are cut into the wild. And I can't be too negative about it, I didn't even have that. I would just say I learned from 20 years of reading and mistakes.

throwawaaarrgh 5y ago
> I would just say I learned from 20 years of reading and mistakes. One thing that's crazy to me is that when people make mistakes, in most cases it's forgotten or swept under the rug. Whereas if they do a full post-mortem and share it with the entire engineering organization, they're teaching everyone a valuable lesson (possibly multiple lessons) for free. If that lesson prevents the same situation from happening again even one time, they'll have "paid off" the first mistake, and it cost them nothing. Free money!
- axaxs 5y ago
  I agree, but it goes back to my initial argument. Even if everyone documented every failure and had perfect documentation, the result wouldn't be a whole lot different. People just don't care or pay much attention until it affects them personally. That's not to say it's a waste. Once a person gets bitten, they look for resources and learn from that. But until then, we're basically all stupid apes making the same mistakes in perpetuity.