3 ms·
I think this is a fine attitude in the short term, and an absolutely terrible one in the long. It's certainly bad for the business; companies that (by your numb
by wpietri 7y ago
I think this is a fine attitude in the short term, and an absolutely terrible one in the long. It's certainly bad for the business; companies that (by your numbers) are happy paying 150% extra in costs will have a hard time competing over time with companies that keep their costs low.
But I think it's also bad for the developer. Giving up and accepting bad code and low productivity means we develop habits and attitudes appropriate to that environment. It keeps us from getting better at our jobs, from keeping up with new technologies and new approaches. And given how our industry keeps changing, I think that's a recipe for disaster.
- deleted 7y ago[deleted]
- vkou 7y ago> It's certainly bad for the business; companies that (by your numbers) are happy paying 150% extra in costs will have a hard time competing over time with companies that keep their costs low. If most of my income derived from being an owner of a company, I would care deeply about this problem. Since it doesn't, its really no sweat off my back, either way. > It keeps us from getting better at our jobs, from keeping up with new technologies and new approaches. In my experience, tech churn is one of the top reasons for why code has gone to shit. "It's been three years since the last re-write, let's rebuild the product again, in a framework that nobody here knows how to use!" On the bright side, both the re-write, and the cleanup of the resulting mess means steady employment.
- wpietri 7y ago> Since it doesn't, its really no sweat off my back, either way. Again, only in the short term. A failing company is not a fun place to be, and a failed one even worse. And if you end up with a resume that has a long string of losers as your employers, it's going to get harder to get good jobs.
- vkou 7y agoDo you think so? If you do, and you hire people, you should seriously consider not thinking in that way. Any manager who can put two and two together should be well aware that the impact that an average IC has on the success of a failing company that's bigger than 100 people is near-zero. It's just pedigree snobbery, to look at a resume, and go: "Oh, well, he worked for losers, he must be a loser, reject."