11–20 of 54 posts
Most of the people getting promoted/going into management arent the smartest or best fit, its just someone willing to gun for it/jump through hoops. So you get those types potentially bossing around someone more competent, odd dynamic
> its just someone willing to gun for it/jump through hoops You mean motivated people with stronger work ethics? There’s a lot more to life than being smart.
Yes well no one asked you to leave some text on a server somewhere and hope someone sees it. They asked if you could do X by Y time and you said YES.
When the team doesn't talk synchronously. So many times I've seen folks post a question that needs swift response to some issue tracker and then act indignant when they are held accountable for the thing not getting done. The answer is almost always "well no one responded until 3 days later". Yes well no one asked you to leave some text on a server somewhere and hope someone sees it. They asked if you could do X by Y…
Of course this usually isn't that much of a problem when the question is not too important, or the asking person knows possible options to proceed - it's usually a new or junior team member who suffers most from this. On interviews everybody is encouraged to ask questions, but in real life many become tired answering something which they know for too long - even though it's the specifics of the system, which they built unnecessarily complicated and just got used to. So unfortunately in subpar teams it becomes harder to obtain necessary information.
Most of the people getting promoted/going into management arent the smartest or best fit, its just someone willing to gun for it/jump through hoops. So you get those types potentially bossing around someone more competent, odd dynamic
> its just someone willing to gun for it/jump through hoops You mean motivated people with stronger work ethics? There’s a lot more to life than being smart.
It's illusion that PR can usually be compact in terms of lines and files. That not only requires a good quality of code, which isn't ubiquitous, but also good understanding of code, which changes all the time with different opinions resulting in that code being modified. So PRs become rather large - and sometimes surprisingly missing useful things, because exact change isn't easy.
The PR which is hard to review may mean that the code isn't understood the same way by different people, and this is a signal that some discussion is needed. Unfortunately often that's not done, and after some efforts PR is pushed through, while misunderstandings grow.
So instead we're just not going to optimize anything, and every tool just gets slower and slower and slower.
Mis-handling of public communications on significant outages.
I don't mean focused retrospectives, which is time set aside to constructively address things worth complaining about.