Guys guys guys!! I ran the windows network diagnostic tool... And it actually fixed the problem!

Worst codding interruptions? That's easy: fucking meetings.

You know they're coming up. They start to drain your focus. You double check the clock/start time. You ask yourself if you were supposed to prepare anything. You typically waste an hour of your time over something that could have been a fucking e-mail (or doesn't even matter at all). You come back to your desk, and your focus is broken and you wonder when the next meeting is coming up.

The tale of mouse and clock

Once upon a time, there was a mouse that wanted to know what time it was. So it asked the first best man, but unfortunately, it didn't understand Suaheli. Anyway, the man just mumbled "gotta kick the cat in the ass".

So the mouse went on and nearly would have got it when another mouse came into play that had been sewed onto an elephant's ear for 27 years - but it had forgotten the exact time it had gotten sewed on.

So the searching mouse came up with doing something about the sun, but since it was just a dumb mouse, it looked into the sun and was blinded for a time.

Somewhat desperately, it staggered through the gutter where there was quite some garbage. Just by chance, it fell over a dumped wristwatch and broke its nose.

Moral of the story: even a blind mouse sometimes can find a broken clock.