2 ms·
I dislike articles like this. They take a situation that isn't representative of the workplace everywhere, generalize it, and come up with a universal "never do
by ineedasername 7y ago
I dislike articles like this. They take a situation that isn't representative of the workplace everywhere, generalize it, and come up with a universal "never do X!" headline that grabs attention.
There's nothing wrong with deadlines, even arbitrary deadlines. Without them it's easy to get lost down a side path of "oh, it would be nice if we could do X". They serve to focus attention. The thing is not deadlines, but how you work within them. If it's arbitrary, Work backwards from the deadline to what can reasonably done, and present a detailed account of those estimates. If you have a hard-charging "just get it done" boss, part of your responsibilities is to manage upwards, educating your leadership on what your job entails so they can have reasonable expectations. Most managers are not actually pointy-haired bosses, but you have to work towards that relationship: if you treat them like a PHB, you'll give them no way to evaluate your work except their own faulty metrics.
Will this work in every situation? No. But that isn't representative of some universal problem with deadlines, it's representative of poor management.
here's nothing wrong with setting dates. There's nothing wrong with setting arbitrary dates
- MaulingMonkey 7y agoEven impossible deadlines aren't the end of the world. "We need X Y and Z done in N weeks!" "...I'm not sure if we can get even one of those completed in N weeks - and that's even before accounting for the fact that I'm an optimist among optimists. Since it's so obviously impossible, I'm not going to kill myself trying - instead, let's talk prioritization, so we can deliver as much value as reasonably possible within the deadline, if it's really an important one." What you want to avoid: 1) Pressuring devs into crunch/burnout/quitting/morale loss/checking out. Turnover will eventually cause brain drain when your best talent leaves for greener pastures, and makes hiring more expensive when your reputation sours. 2) Pressuring devs into sacrificing long term productivity for meaningless short term milestones. It's one thing to prioritize a feature or two for an important presentation to investors who will be making decisions about your financial future at the temporary expense of, say, test coverage. It's another to do so routinely that codebase stability suffers, developer velocity gets wasted on disturbingly routine debugging sessions, and build engineers disable code coverage metrics for being "just too gosh darn depressing to even look at."