Saying "no" and knowing how to do it correctly is the most important skill in my opinion. I have emails popping up all the time, interruptions everywhere, no time management method and yet I am the most productive of my team when it comes to development.
But saying yes at the wrong time - and it get's downhill rapidly. More to implement = more time pressure = less quality = more bug fixes = more time pressure, etc...
So turning a no to a yes if possible is the better way. But be warned: doing it too often may also lead to unwanted expectations of your manager/lead/product owner.
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.
Saying "no" and knowing how to do it correctly is the most important skill in my opinion. I have emails popping up all the time, interruptions everywhere, no time management method and yet I am the most productive of my team when it comes to development.
But saying yes at the wrong time - and it get's downhill rapidly. More to implement = more time pressure = less quality = more bug fixes = more time pressure, etc...
So turning a no to a yes if possible is the better way. But be warned: doing it too often may also lead to unwanted expectations of your manager/lead/product owner.