The schedule below isn’t the full picture because I normally go on call every few weeks. I spend on call days communicating with other teams and resolving incidents. Bi-weekly attending meetings related to on-boarding, recruiting tech talks, and all hands. I only read work email in the morning unless someone PMs me to review. My company also uses Slack for communication and I limit my time on there as well. This facilitates minimizing distractions and intaking too much information. Days when I’m physically tired stem from being mentally tire from context switching. It is difficult to reach me throughout the day, if it wasn’t scheduled in advance.

Writing code, researching and documenting consist of anything between code reviews, writing configuration, rpc services, dashboarding, design docs, etc. If I arrive late or early, the schedule adjust. Most teams perform retros at the end of a sprint. I peform self retros daily since I look to complete a task per a day. I am able to easily remember what I did today and how I felt about it. It sucks being in a retro two weeks later, and having to dig through my thoughts to remember what I worked on and what went wrong. My downfall at times is not ending the day when I know I should. I’ve started setting goals outside of work that begins in the evenings. When I’m not on call I even leave my laptop at works.