The frontend code review checklist I wish I had as a junior dev

So, back in 2017, I finally graduated from university and got my first job as a junior dev. At the time, I had to learn everything the hard way, such as good practices, code review guidelines, writing good commit messages, and so on.

Today I'm writing about my experience with code reviews since I was a junior dev and all the way to where I am today.

So my first experience with code reviews was a total disaster... not gonna lie, I used to just look at the code that I had absolutely no idea what was it doing, and just hit approve hoping the senior dev would just think I actually read the code.

Then as I got a bit more comfortable and more experience, I started to actually look at some parts of the code and started identifying some bad practices that could be improved, but didn't quite catch bugs and every piece of bad code.

Over the time, I got much better at code reviews and started to actually catch bugs, bad practices, code improvement opportunities via design patterns, etc.

I've been documenting some key points for code reviews along the way, and put them all together in a single file.

That's how I created The Frontend Code Review Checklist to help other developers in every level (jr., sr., tech lead, even freelancers) so that fellow developers won't suffer what I suffered!

Check out my product in Gumroad!

I really hope it helps you guys out there with your code reviews, and I truly appreciate your support!

Happy coding! :)