I hate how disruptive meetings are, I was coding and now I don’t know what the fuck I was trying to do.

Just keep working!

You were discussing something with the Men In Back and then there was a sudden bright flash!

@PonySlaystation Now the Men In Black needs to flash you too...

@Grumm fuck. I outed myself 🙈

My job has me attending 14+ meetings a week, and my input only matters in one of them. The meetings are also all spread out, and yet management wonders why I don’t get enough done.

Gee, maybe it’s the meetings I keep complaining about? Right, last time they listened about that, they missed the meeting part and just added another one.

Now that I have a new (micro)manager, I have yet one more meeting! Fucking fantastic.

Management: "You need to attend this meeting, it is very important."
Dev: "Are you sure? Got a lot on my plate right now."
Management: "Yeah it's a must."
Dev: "Ok, I trust your judgement."

*Proceeds to get stuck in a 1 hour meeting on management trying to justify why coming back to the office will improve productivity*

Look back at your IDE and git log?

Sounds like you need one extra meeting for finding out what the fuck you're trying to do.

I deal with constant interruptions all day..

What works for me is to write out a _really rough_ plan/ notes/ some form of sudo code -depending on the work I’m doing _before_ I start coding..

While I’m taking notes, I take screen shots of places that I’ll need to touch.

As I work through the “plan” I check off what I’ve already competed.

It’s not perfect, but this approach gets be back on track in a few minutes, and let’s me easily pivot when I randomly get told the priority of my assignments have changed.