"Hallway meetings" (even if virtual) which do not include all stakeholders and at which nothing is recorded. Just "oh yeah we decided" a week or a month later. When I was in a position to do so, my answer was "no you damn well did not".
Ask HN: What practice by a tech team pisses you off to your core?
51–54 of 54 posts
Re: Ask HN: What practice by a tech team pisses you off to your core?
#52Scheduling {anything} for release in the 4th quarter.
It isn't going to make it, and it will annoy/discomfit/make life miserable for everyone.
Re: Ask HN: What practice by a tech team pisses you off to your core?
#53micromanagement. Hate it when director joins regular meeting and brings a lot of confusion with their little domain knowledge but speaking loudly thei ideas... And also when people try to understand what business value brings shifting a button from right to left and talking about it for 40min.
>>And also when people try to understand what business value brings shifting a button from right to left and talking about it for 40min.
"Bikeshedding." Ever since I learned that term I realized how much of my meetings are just that :(
Re: Ask HN: What practice by a tech team pisses you off to your core?
#54Changing code you have committed working on (as can be seen in the product management tool) without notifying you, which makes git return hundreds of merge conflicts when merging the main branch into your work branch -- basically ensuring you either can start over again based on the new code or risking drama when force rewriting the main tree without said unexpected changes.
Worst time it happened to me was the day just before the start of my Christmas holiday and it almost made me quit.