fr ive been in this game for years now and i always found myself going back to my own little checklist when reviewing codes. u know, those standard six things everyone talks about - tests? naming conventions? style guides. all that jazz is important stuff but its not where the real bugs hide.
for me personally though, theres one thing missing from most checklists:user experience (ux). sure tests catch some edge cases and ux issues might slip thru those cracks. ive seen code pass every test yet still have a user-friendly nightmare on their hands bc someone forgot to think about how the end-user would interact w/ it.
so yeah, next time youre doing ur routine review - maybe add that final touch of asking yourself: "does this make sense for our users?" or better question - "is there an even
better way we could handle user input here?"
what do y'all usually prioritize in code reviews?
link:
https://dev.to/pixel-wraith/the-code-review-checklist-i-actually-use-9ok