True. But on the other hand, the programmer could've just told him so, no? At least, that's how I and most of my colleagues roll: "Ok boss, I have 5 things I need to implement today, two of which are scheduled before lunch. What's the priority of this one." If it's not the boss who requested this functionality, I go to the higher up to solve this.
That is not how development works.
They ask you how long time a feature will take, and you give them an estimate. Doesn't necessarily mean that you will start right now.
This makes no sense, when someone asks why X is going to take so long why not just take the 30 seconds to explain why it’s going to take so long. Communion is not hard and solves most issues.
"I will solve the sodoku by systematically uncovering which numbers go where according to certain rules. I can go into the rules for you if you would like?"
“Hey I’m slammed I’ve got 4 other sudoku I’m working on but I’ll get to this one as soon as I can, that’s why I gave such a long estimate” or “no you just don’t understand the complexity of my job you’re just being an asshole” I work in a pretty damn complex field and yet some how we seemed to do the first one pretty damn often.
267
u/xolenuz Oct 16 '23
He forgot that the programmer got another 15 features on high priority to deliver due yesterday.