Today was an eventful and productive day! I wrote two lines of code! 🤣 I'm completely serious regarding the fact that today was very productive, though. I reduced our ESD queue by ~30% simply by investigating issues and communicating with those who had opened the ESD tickets. Furthermore, I was able to assist with debugging an issue that has been stumping our team for weeks. I can't take much credit here as a fellow engineer who I encouraged to take the lead on this initiative led the way, and we had incredible support from an engineer from another team. Finally, I briefly presented a small piece of our revamped hiring process to a large group of Auth0 engineering managers. To aspiring engineers, more often than not, it's not about lines of code written; there are many other ways to have a massive impact as an engineer!
Now it's time for one of my favorite topics: failure! Again, I'm serious. 🤣 Many of the most impactful moments of my life resulted from failure, or rather from how I reacted to these failures. I failed as an aspiring actor when I lived in LA, but I met the woman who would soon become my wife in the process. I failed as an actuary, but this led me to pursue launching a startup. I failed at said startup but learned to program in the process. I failed at my first few interviews as an aspiring engineer, but eventually, everything clicked when I interviewed with Circle. I'm so grateful for the early failures and that this was where I was fortunate enough to spend my first 4+ years as an engineer. While moving on from Circle, I failed in interviews with Apollo and Stripe before succeeding when I interviewed with Auth0.
This may very well sound cliche, but the only way to truly fail is to neglect to learn from your failures. So if you're currently struggling to launch your career as a software engineer, just know, we have all been there. We have all failed multiple times. We have all doubted ourselves more than once. Keep your chin up, learn from your mistakes, and if you need some one-on-one advice, schedule some time on my calendar, and we can talk through things!
(Pictured: me failing my first ever squat attempt at a sanctioned, drug-tested powerlifting competition. I ended up failing due to re-racking the barbell too quickly, not because I failed to squat the weight. Attention to detail folks, don't neglect it!)
Now it's time for one of my favorite topics: failure! Again, I'm serious. 🤣 Many of the most impactful moments of my life resulted from failure, or rather from how I reacted to these failures. I failed as an aspiring actor when I lived in LA, but I met the woman who would soon become my wife in the process. I failed as an actuary, but this led me to pursue launching a startup. I failed at said startup but learned to program in the process. I failed at my first few interviews as an aspiring engineer, but eventually, everything clicked when I interviewed with Circle. I'm so grateful for the early failures and that this was where I was fortunate enough to spend my first 4+ years as an engineer. While moving on from Circle, I failed in interviews with Apollo and Stripe before succeeding when I interviewed with Auth0.
This may very well sound cliche, but the only way to truly fail is to neglect to learn from your failures. So if you're currently struggling to launch your career as a software engineer, just know, we have all been there. We have all failed multiple times. We have all doubted ourselves more than once. Keep your chin up, learn from your mistakes, and if you need some one-on-one advice, schedule some time on my calendar, and we can talk through things!
(Pictured: me failing my first ever squat attempt at a sanctioned, drug-tested powerlifting competition. I ended up failing due to re-racking the barbell too quickly, not because I failed to squat the weight. Attention to detail folks, don't neglect it!)
