4 ms·
I didn't read the book but I tend to disagree with 1. - I've seen a lot of well standardized projects fail. And a lot of disorganized projects succeed. Failure
by GuB-42 7y ago
I didn't read the book but I tend to disagree with 1.
- I've seen a lot of well standardized projects fail. And a lot of disorganized projects succeed. Failure with standardized projects are often attributed to "not followed the standard properly", but if following the standard is so complicated that most teams don't, maybe something is wrong with the standard.
- Retraining is not a bad thing. In the end, employees who have seen many different work environments are generally more skilled. You need to think long term, even considering today's lack of loyalty for employers and employees alike.
- One single language is a stupid idea. Use the right tool for the job. For an experience developer, switching languages is not that hard anyways.
Anyways, I don't think point 1 is bad advise, but we also need to apply point 5 to it ;)
- bradknowles 7y agoFollowing a standard is not a guarantee of success. Not having a standard to follow is also not a guarantee of failure. It is possible to succeed without a standard. And it is possible to fail if you do have a standard. The key is that having standards (not just “a” standard) usually increases your odds of success. To the point that many feel that having standards is a functional requirement.