I forgot how nerve-wracking preparing for interviews was, especially technical interviews. As I'm going over old code and writing new code, I fall into this rabbit hole when looking things up. Whether it be in documentation or Stack Overflow, I have this habit of just trying to learn more about what I just looked up, and then the documentation mentions something that I find interesting and I look that up...and the cycle continues until I'm confused out of my mind and wonder what the heck I just read.
The best part about being a software engineer is that I can deliver quality software and experiences to the client, but very close up there is being able to constantly learn in an ever changing environment. This comes with it's pros and cons. On the top end, I get to better myself and expand my knowledge and skills. But on the other end, There's so much out there that I don't know (and the worst part is, I don't know what I don't know). This ties in with job hunting, because as the interviewee, we never know what is considered "the bar" or the "standard" for getting hired. We never know how well other applicants are doing. It's pretty much always trial by fire since all companies expect a certain level of technical ability, and trying to prepare for everything is usually the only option.
This isn't really a rant, it's just a realization as I study up for my upcoming interviews. I'm grateful for all the opportunities I've been given, and if I don't do well I just have to learn from my mistakes and keep positive.
Looking for a chance to learn in everything.
Leave a comment if ya'll have any thoughts or insight about this!