I wonder if traffic shaping on a linux router could help pushing back download traffic. The article at digitage.co.uk/rope/BlockingBittor... seems to have a filter, but I would budget a solid day for getting this set up and tested (assuming you have the linux box already on your network).
About Procrastination: In my ebook Programming Without Anxiety I cover six specific reasons of procrastination, along with guidance on avoiding them.
On the website you can get a free sample as well, which addresses five major sources of workspace anxiety. If you like it, subscribe for updates!
As for closing everything at the end of the day: that's one possible strategy, has the advantage that it forces you to leave your work properly cleaned up. But don't forget to push all commits on a working branch beforehand, maybe even send PRs so you are greeted with review comments the next day (which is a good boost to know where to pick up work).
The other benefit is that if reopening everything is cumbersome, you are likely to start looking for shortcuts and optimize the development flow.
Good luck! You can soften the message by writing "don't schedule". At Google you could just put "DNS" or "Make time" on the calendar and people got the message.
If the company culture is less receptive to this, you can try adding a more cryptic name, like "task discussion" and reserve a meeting room for uninterrupted time.
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.
I wonder if traffic shaping on a linux router could help pushing back download traffic. The article at digitage.co.uk/rope/BlockingBittor... seems to have a filter, but I would budget a solid day for getting this set up and tested (assuming you have the linux box already on your network).
About Procrastination: In my ebook Programming Without Anxiety I cover six specific reasons of procrastination, along with guidance on avoiding them.
On the website you can get a free sample as well, which addresses five major sources of workspace anxiety. If you like it, subscribe for updates!
As for closing everything at the end of the day: that's one possible strategy, has the advantage that it forces you to leave your work properly cleaned up. But don't forget to push all commits on a working branch beforehand, maybe even send PRs so you are greeted with review comments the next day (which is a good boost to know where to pick up work).
The other benefit is that if reopening everything is cumbersome, you are likely to start looking for shortcuts and optimize the development flow.
I read your sample book. The one that I really like and I'm planning to do is the "Do not disturb" one.
Good luck! You can soften the message by writing "don't schedule". At Google you could just put "DNS" or "Make time" on the calendar and people got the message.
If the company culture is less receptive to this, you can try adding a more cryptic name, like "task discussion" and reserve a meeting room for uninterrupted time.