News for hackers. Stuff that matters.
Re:Rules for Developing Safety Critical Code [pdf] by jwdunne on Friday January 16, 2015 @08:08AM (#8898589)
Actually, the use for that doesn't seem restricted to software in general. It seems like you could apply that to any team and get better results - for example, if a big sales deal falls through, don't punish the sales person, use the situation as a learning experience.

I try to do this with my team as much as possible. I am limited by my superiors, who don't hold the same beliefs about maintaining morale and intrinsic motivation.

Re:Rules for Developing Safety Critical Code [pdf] by pilsetnieks on Friday January 16, 2015 @08:19AM (#8898638)
It is also known as kaizen, with the Toyota Production System[1] as the best known example.

[1] https://en.wikipedia.org/wiki/Toyota_Production_System