Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

No, what we're talking about is (to extend your very condescending tech support analogy) shipping the customer a new PC from the factory, and telling them to throw the old one away because it doesn't matter. It will only start to matter if they have 3 bad PCs in a row, at which time it becomes (a) a demonstrable failure and not just stray neutron rays (b) an incident which will carry a postmortum of how the organization could have prevented that failure for next time

I did start the whole thread by saying "and then I grew up," and not everyone is at the same place in their organizational maturity model. So, if you're happy with the process you have now, keep using it. I was unhappy, so I studied hard, incorporated supporting technology, and lobbied my heart out for change. Without maturity levels we'd all still be using telnet and tar based version control



Once you reach the next maturity level you realize that some problems and bugs are from bad design, and cannot be fixed by restarting the server.

Fixing bad design is an art, not an organizational discipline. (Sadly.)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: