I do have some anxiety about the largely differing nature of the two roles I'm attempting to fulfill and the risk of having both at the same time. The Scrum Guide says the Scrum Master can be on the Development Team if they are executing the work of the sprint, so I'm not playing outside the rules of the game. Nevertheless, a mentor of mine has suggested that being a Developer means you have a list of deliverables that are easy to check off one at a time, but being a Scrum Master is far less task-oriented and involves a people-oriented set of skills such as mentoring, coaching, facilitating, and educating. As a result, it's easy to focus on the Developer's deliverable list and forget to prioritize the Scrum Master's duties.