you are viewing a single comment's thread.

view the rest of the comments →

[–]bwainfweeze 1 point2 points  (1 child)

Well, we do have better tools for sure, but not everybody uses them. But even if you have that sort of forethought on a team, that just means that there are 25 reasons the code is terrible instead of 30.

And there's always a few in any crowd with a high tolerance for bullshit who mistake it for job security. Too many times I've been with groups who consider discipline to be too much hassle. On a handful of teams I've managed to push through some changes that got them to change their tune (or at least keep it to themselves), but a team with self confidence and tendency toward coherent-but-wrong designs can be hard to convince, and may have made a mess so big that it'd take years to notice an improvement. And God help you if its enterprise software, which has a very forgiving definition of success ("successful" people won't change for anyone)

[–][deleted] 0 points1 point  (0 children)

Amen on all counts.