4 ms·

I think you're being a bit too hard on Ed. A lot of things need to be answered. How many times has this happened that he's had to deal with? How many times ha

I think you're being a bit too hard on Ed. A lot of things need to be answered. How many times has this happened that he's had to deal with? How many times has he tried to explain to his boss that things take a lot of time? How many times has he tried to help and only confused them more? How many times has he been reprimanded by his boss for trying to help with these tasks? Also, how is Ed lazy? The chance of needing to speak up at a given moment is so high he couldn't adequately do another task, especially a programming one, or any task that requires a high amount of focus.

gaelen224 15y ago
You are right. It is a little too harsh toward Ed. I think the general point is correct, though. The management failure here is much deeper. The culture apparently tolerates interruption of important work. Firedrills over relatively trivial problems. Leaning back and watching teammates fumble. And just generally not solving problems in efficient ways, looking for and resolving root causes. It is clear that Ed is not happy or fired up. The company sounds lame. I'm sure this is not the first time something like this has happened. Otherwise, why complain about it? And rather than leaning back and watch the slow motion car wreck over and over, I think erdevs is right... this is pretty lazy and lame. The company sounds lame too. Seems like the Hacker Way would have Ed either leaving such a lame place, or intervening at this place to try to help level the company up as best he can.