3 ms·
I know so many people who are in this exact position. Trying to change the practices of their companies for the better but never getting anywhere. A client is
by rawfan 6y ago
I know so many people who are in this exact position. Trying to change the practices of their companies for the better but never getting anywhere.
A client is paying for a refactor but the manager says "we don't have time to write tests, the client is not paying for that" (when indeed they are in the end).
- brendt_gd 6y agoI feel like company's like that are shooting themselves in the foot: the delivered product is of lesser quality, developers aren't happy and quit sooner or later. Looking at it from a manager's perspective, I think you'd want to do everything in your power to prevent such situations. Feels like there's a general lack of future perspective in many companies.
- Cthulhu_ 6y agoThe client IS paying for that; the trick is to not end up in a situation where a refactor becomes a rewrite but part of your daily job. A refactoring shouldn't take more than a couple of days; if it does, it's too big. Same with testing. The client does not pay for refactorings or testing, and your manager shouldn't be made aware of it because it's part of your regular job. If they have so much insight in your day job that they start complaining, they're micro-managing and probably redundant (if they have the time / energy to look as closely at you / your team's work).
- 9dev 6y agoWell, I have seen both sides of this story by now: at my previous job, we had lots of developers who are happy to throw the whole code base over board every two months as they discover a new test framework, spend a month on refactoring simply to satisfy a single dev‘s pet peeve for functional programming... it’s especially frustrating to watch as a team lead from another department, actually understanding what’s happening, but unable to do something.