2 ms·
On the contrary, there are plenty of devs who won't take on any work until it's been designed, scoped, run through management, prioritised and scheduled, when t
by maccard 8y ago
On the contrary, there are plenty of devs who won't take on any work until it's been designed, scoped, run through management, prioritised and scheduled, when the actual fix is a one line change that would have taken less effort than the meeting where it was prioritised.
There's a happy middle ground between the two, and assuming developers who will deliver quick fixes are all hacks who don't care is counterproductive.
- hinkley 8y agoThose people got burned by managers who like to think that all of their problems are one line fixes that can be rushed out. They think that 'simple' from the user's perspective is 'simple' from an engineering sense and usually those are inversely correlated. Essentially that engineer has grounded the management team. They can't be trusted to behave so their toys have been taken away.
- commandlinefan 8y ago> There's a happy middle ground Yeah, the happy middle ground is a management infrastructure that doesn't insist that you say exactly how long everything is going to take before you start doing it and accept that there ARE unknowns in software development.
- megablast 8y agoHa, hilarious. I have had changed that were done as soon as they were mentioned, but still required several more meetings to ensure everyone was aware of the upcoming change, had signed of on it (even though it was a severe bug), and discussed it ad-infinitum. Including how to do it, even though I already did it at the start of the meeting. Approximately 100x the time it took to do the work.
- bfdm 8y agoWell, sure. I've had those too. The trick is making sure some of that time is spent validating the assumptions you made explicitly or subconsciously. Doing the change right means making sure that a) your change actually meets the request as the requestor understands it and b) doesn't break other features that already exist.