1001 Ways To Remind Myself I Want to Be a Software Engineer

Do you know the story of Scheherazade? Of 1001 Nights?  Of the Princess who married the king who wanted to have her executed? But every night she told him a story and he wanted to know the ending. And so he spared her. Sometimes in my career I have felt like Scheherazade. Always reassuring people that things are about to click. That the results are about to come through.

Every night another story. While we wait for my learning style to catch up. And look I hate changing teams. I hate changing companies. I hate changing jobs. And hopefully I won’t have to do any of this for a while. And if I do then somehow I will have to survive. But maybe soon 

I’ll get to stop promising. And get to actually really start delivering those impressive results really soon.

I’m going to do something I very rarely ever do. I’m going to share a screenshot from the last blog post. Just the last one but one:

I want to zoom in on this one goal please. But first - Horchata. Look 

So let’s say that my goal is daily commits 

This is the process my manager has described for me. Apart from committing daily which I still want to explore a little bit more with a manager who mentors me on Monday. And just want to process for myself exactly what that means. But let me talk about the other bit of it - the GitHub bit which my manager has described. Starting and ending my day with GitHub. And learning to focus on it as my main tool for work each day. Here are the steps.

Steps for using GitHub as my main tool at the start and at the end of each day

Throughout the day I should be committing to my repo. Or at the end of the day whatever I have done I should commit it and push it. The idea then is that I have done something every single day. Is that I have written some code every single day. No matter what. And then that

• At the end of the day I should push those changes
• At the end of the day I should write some comments on what needs to be done
• If there are changes that need to be made on a line of code or questions about a line of code I should comment on that line of code
• If there are changes to by made on a whole file or questions I have on a whole file then I should comment on the file
• If there are broader questions or steps then I should just comment generally on the PR
• The next morning first thing when I come in I should look at the code, look at the PR, look at the comments I have written 

And write out my next steps please. Thanks

Anyway I just need to stop writing about it and to do it. And hope for the best. And hope that for once after all of this long time this finally will click. And not be too hard on myself - because that’s what a colleague told me to do. To not be too hard on myself. Thank you guys

Everything takes time