1. Software

7 min read

Knowledge Gaps: 2022 Edition

The more you learn, the more you realize you don’t know… I wanted to share some things I don’t know (but probably should) in 2022.

This post is heavily inspired by Dan Abramov in his blog Overreacted. It is a great idea to admit your faults and identify your gaps in understanding. It might give you some areas of focus to improve your skills in your field and it’s also a good reminder that you don’t know everything. No one can know everything and even the most experienced may have gaps or incorrect mental models.

Personally, I am constantly in flux between the so-called Imposter Syndrome and the I AM A CODER GOD overconfidence. I try to remind myself that there is a TON I don’t know… but there is also a lot that I do know and skills that I have built up over the years that have turned me into a valuable engineer. As long as you are aware of your knowledge gaps and are willing, or better yet, excited to learn new things and become better than you were yesterday, you will find success.

I thought Dan showed a lot of bravery in opening up about his knowledge gaps and possible insecurities so I decided to do the same in this post. Here are a few of my knowledge gaps in the software world:

There is still so much more I have not included on this list but those are some of the highlights. I encourage you to take some time and think about where your knowledge gaps are. Always remember that if a project or task comes up that requires some knowledge, you can always learn and start to fill these gaps. These gaps don’t at all devalue the skills you do have. Play to your strengths as much as possible and slowly start to fill these gaps as needed. I think in a year or two, I will write another post to see how my gaps have changed as my career progresses. I imagine the list will get longer.