Last week was a real challenge but I am in a way better position this week. Back in the gym and closing in on my milestones at work. Soon it’ll be December and I’ll be back in San Diego with my friends and family celebrating a year of excellence. Till then, let’s get to work ✌🏻
Had some time to reflect on my struggles with my current work project and this quote resonated with me: "Experience is the best teacher, and the worst experiences teach the best lessons"
#SoftwareEngineering#ProfessionalGrowth
Day 6 of #100DaysOfCode application decided to break in multiple ways and additional logging was required to determine root cause. Frustrating when rollouts refuse to go smoothly but I live for the challenge.
Day 4 of #100daysofBoxing killin it in the gym tho 🥊 #hustle
Also there’s no hot water at my apartment for some reason so it’s cold showers for the time being until I get it fixed but I suppose it’s good for me. . .
Day 5 of #100DaysOfCode wrote a powershell script to delete logs older than 7 days and schedule it to run everyday.
Day 3 of #100DaysofBoxing feeling like I’m getting my conditioning back.
Let’s finish the week strong 💪🏻
Day 4 of #100DaysOfCode was mostly documentation. Hard to do much with work being busy and hitting day 2 of #100daysofboxing Little by little we gaining momentum tho 🙏
Day 4: Just woke up feeling like I went a few rounds. 🥴 Last night, I updated my Pops business website and updated users: https://t.co/PJvdFyDcg8 💻Today, diving into some personal .Net projects. Time to show these coding and fitness hurdles who's boss! 💪 #100DaysOfCode#grind
@Unnati_twts While clear comments can be helpful, investing in thorough documentation and well-crafted code structure can often make comments more of a backup plan. Thoughts?