I start my day in email and Slack to make sure nothing requires my immediate attention. Then, I switch gears to customer support for a predefined amount of time, usually 90 minutes or so. Then, I look at what PRs are waiting for review or bugs that have been reported. I check in with my team to see if they need anything from me or if I can help with anything they're working on. I don't usually jump immediately into coding because by this time, it's nearly lunch time and I won't be able to find any groove to work in. If I can't think of anything else, I go to lunch early.
After lunch, I may have meetings or something like that, but otherwise, I get into coding mode. I usually have some larger task that is spanning more than a day that I need to pick up, so I launch into vim and get to work. Seems like not too long after that, time has usually flown by and it's time to stop for the day and do it again tomorrow.
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 start my day in email and Slack to make sure nothing requires my immediate attention. Then, I switch gears to customer support for a predefined amount of time, usually 90 minutes or so. Then, I look at what PRs are waiting for review or bugs that have been reported. I check in with my team to see if they need anything from me or if I can help with anything they're working on. I don't usually jump immediately into coding because by this time, it's nearly lunch time and I won't be able to find any groove to work in. If I can't think of anything else, I go to lunch early.
After lunch, I may have meetings or something like that, but otherwise, I get into coding mode. I usually have some larger task that is spanning more than a day that I need to pick up, so I launch into vim and get to work. Seems like not too long after that, time has usually flown by and it's time to stop for the day and do it again tomorrow.