this post was submitted on 21 Oct 2026
37 points (100.0% liked)
Programming
28911 readers
428 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've done thousands of reviews, been a senior for the last 4 years, and a tech lead for three of those. If I could distill what I've learned into a few tips:
Make sure you understand what you know what they're doing and why they're doing it.
If something feels weird, explore it, your gut is a leading indicator of bad code.
Think about how you would know if there was something wrong with the code after its deployed.
Think about how hard it would be to change the code later on.
Those are probably my big ones for general code reviews, there's more specific ones for v&v and embedded, but I feel like these apply to everything.