This last month has been an emotional rollercoaster for me. As a person who has focused heavily on chasing after her professional goals and figuring out her professional identity in the last few years, I’m learning a difficult lesson: do not put all your eggs in one basket. While I practice this when it comes to my financial investments, I do not practice it when it comes to my personal and professional life.
In this challenging and unpredictable year, I’ve stared at my computer more than I care to admit. My time spent on connecting with others diminished. I’ve put…
Ughhhh. One of the most frustrating things about learning to code is seeing a bunch of errors and stack traces. I used to freak out and not pay close attention to them because they were daunting to me. However, when I take one stack trace at a time, it’s not so bad. Stack traces are intended to help us learn where the exception came from.
Here’s an example: