How to Pass Code Review on the First Try

Submitting code for review can be a nerve-wracking experience, especially if you are early in your coding career or new to a larger company requiring a code review process.

Having a development career and working on side projects are two completely different things. If you are working on your own project it's easy enough to have an idea, slap some code together, and push it up. Nobody else cares and life is simple.

When your job is coding, your code probably has a tangible impact on the bottom line of the company or the customer’s experience. This usually means that your code will be scrutinized much more thoroughly before it actually makes it to production.

This is why it’s super important to do your own code review before pushing the big green button on GitHub. Before submitting your next code contribution, try these steps. They’ll not only make you look like a hero but also save precious time for both you and the reviewer which is excellent for your career.

[MakeItStik]

Nice short video.. would love to see you review some code or things you look in code reviews

[jan_Sanku]

I can't believe you're only at 2.45k subs... And less than 1k views? Your channel is severely underrated. Your videos are to the point, factual and high quality. I'm sure it's just the alg being weird, so keep it up, I'm sure you'll get the coverage you deserve!

[Josh-ogeo]

Loving this channel, starting my first role in September so thanks! Feeling a little less anxious

[animeshrose]

Thank you so much for bringing out clarity in this area. Cheers!!

[syncmaster]

Interesting, I always thought LGTM meant "looks good to me".

[Josh-ogeo]

I’m not sure what your plan for content is but I’d love to see a short video on testing/debugging

[Alislaboratory]

Super underrated channel! I just got into contributing to open source projects and Im about to make my first PR! Hope it goes well :)

[daheels]

I'm trying to look at some video that shows what happens when, after submitting for a PR, either the requester sees something that would be best done differently than was originally described or there is an error in the code, how is that hangled with git/github?