These kind of days I’m hardest on myself. Didn’t even hit the gym.

Advice that I was given before is walk away, get your mind off of it and go at it fresh the next day.

It’s ironic what made me a top performer in the military and private sector is also what it feels like it absolutely destroys me.

gergelyorosz.gumroad.com/l/engguidebook

My job is to help make my team (Security Incident Response) be as effective and efficient as possible. if I can make the software engineering team that reviews my code be as smooth and easily digestible when reading my PR, I should have a higher chance of shipping code which in turn helps my team.

1. Send PRs in smaller chunks. I usually send PRs in bigger code chunks that get complex and bogged down in administrative task (review, corrections, discussions, etc). Smaller PRs was suggested in the book.

2. Ship everyday. I usually work in long iterations before I submit a PR. Look above

I stopped adding random people and only connect with people I know personally or met in person, upped my privacy on there and noticed most of my noise has been filter down to my interest. Not that I log on all that much, but it’s cool to keep up with people I know.

Is it worth it? Depends I guess.

I will tackle Automate the Boring Stuff or Python Crash Course. DSA in Python book is also on the radar

#pythonprogramming

Thanks, Drew!