3 ms·
The week of wrap up and the week of maintenance is so important, and has basically never been there at places I have worked. Managers reading this - if you con
by malux85 3y ago
The week of wrap up and the week of maintenance is so important, and has basically never been there at places I have worked.
Managers reading this - if you constantly jump from new features to new features you will ensure that your developers are forced to cut corners, make an unmaintainable mess, increase bugs, development velocity will slow and developers will burn out.
It also causes incentive alignment problems, if I push myself to deliver great quality on-time, and I’m striving and working hard, then I don’t get so much as a “well done” and then an immediate enormous chunk of new work - you’re rewarding hard work and quality with large amounts more work, what’s my incentive to perform? Exhaustion?
- perrygeo 3y agoI feel the same way, but the countervailing force is significant group of managers and developers alike who really truly hate spending any time without a rigid structure. Having never taken the time to build a proper mental map, they are lost without a detailed literary. They're allergic to open-ended tasks and use process as a crutch for their lack of confidence. Dealing with ambiguous technical problems is scary; there is a real prospect of failure, or going the wrong direction, or hitting an organizational blocker, or failing to anticipate changes... Some would rather work on an assembly line (and force their colleagues to as well) just so someone else can shoulder the responsibility for the hard problems. And their numbers are large enough to influence how software is developed.