123 karma · joined May 3, 2019
Micromanagement plays out as a constant barrage of needing to be updated on every single detail that you work on. It's immensely tiring, and essentially comes from the manager not really trusting you and exercising too much control. They need to know about every action you take and how long is it taking (and why is it taking X long). It's horrible and drives people to look elsewhere. Project managers also fail badly at this. They badly manage the customer and try always be a 'yes' man to every whim they have, and end up driving the engineers crazy by wanting constant updates hour by hour.
"Some pro-remote people also say "I don't need the social interaction"
I think this is a good point. It's important to meet people in person and then you learn the niches of their character and won't find yourself trying to find translate the intent of someone typing in slack ("is that sarcasm or are they really upset?"). My engineering remote team resolves this by us having twice yearly meet ups, where we all spend a week together eating, drinking and discussing strategy.
For me this is the biggest plus of being on my own: https://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt... I am in full control of interuptions .
Its based on a entire language which is about to go EOL (Python 2)
Changing the name space would have been problematic, as so many people use automation tools now to install package dependencies, rather than break their work because someone has zero intention of maintaining a project, they did the right thing and used the same namespace.
Had this been a case of RH disagreed with the developers direction or any factor around an active project, it would have been a shitty move, but considering the developer ignored any offers to help and let the project to fall into a stale un-maintained state, I don't see any grounds for him to throw his rattle out of the pram and blame RH here.