The only thing I really dislike are meetings where nothing is decided and nothing happens as a result. The best meetings have at least one action step because that means there is some forward momentum even if it is just one little baby step.
The only thing I dislike more than the above is the next meeting where those who had something to do from the previous meeting did absolutely none of the action steps. The outcome of such meetings is the exact same set of action steps from the previous meeting. And tends to lead to no forward progress made for multiple meetings in a row.
I also somewhat dislike how some people see they have a meeting later that same day and start blasting out a bunch of emails to get their previously assigned tasks done in advance of the meeting. I'm pretty sure those people are the sort of folks who waited until the last minute to do their homework for school (sometimes 5 minutes before the next class started). I understand that sometimes it's not possible to do due to a very busy schedule but it should be rare rather than a constant. The behavior also indicates what those people think about the priority of the project. They might say the project is important just to sound good but it's clearly not a priority for them.
On a software development front, the only thing I dislike is spending 6 hours on a bug only to find I mistyped a variable name by one character - or something equivalently braindead that I should have spotted immediately but didn't. Sure I get paid for those 6 hours but it's a massive waste of time and money. It happens but I don't have to like it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The only thing I really dislike are meetings where nothing is decided and nothing happens as a result. The best meetings have at least one action step because that means there is some forward momentum even if it is just one little baby step.
The only thing I dislike more than the above is the next meeting where those who had something to do from the previous meeting did absolutely none of the action steps. The outcome of such meetings is the exact same set of action steps from the previous meeting. And tends to lead to no forward progress made for multiple meetings in a row.
I also somewhat dislike how some people see they have a meeting later that same day and start blasting out a bunch of emails to get their previously assigned tasks done in advance of the meeting. I'm pretty sure those people are the sort of folks who waited until the last minute to do their homework for school (sometimes 5 minutes before the next class started). I understand that sometimes it's not possible to do due to a very busy schedule but it should be rare rather than a constant. The behavior also indicates what those people think about the priority of the project. They might say the project is important just to sound good but it's clearly not a priority for them.
On a software development front, the only thing I dislike is spending 6 hours on a bug only to find I mistyped a variable name by one character - or something equivalently braindead that I should have spotted immediately but didn't. Sure I get paid for those 6 hours but it's a massive waste of time and money. It happens but I don't have to like it.