Technical debt. Keep it minimal, and when needed, write a task for it to be looked in to later.
Coding standards. Don't submit code that has rando extra lines and things that will slow down the next dev from looking in to the past to learn what does what.
And most of all, make sure edge cases are covered, often via a truth table of all possible outcomes.
I often comment on a PR saying "blah blah, but not blocking" so I'll allow it but at least my entitled opinion was known in case that code issue comes up later.
Coding standards. Don't submit code that has rando extra lines and things that will slow down the next dev from looking in to the past to learn what does what.
And most of all, make sure edge cases are covered, often via a truth table of all possible outcomes.
I often comment on a PR saying "blah blah, but not blocking" so I'll allow it but at least my entitled opinion was known in case that code issue comes up later.
My PRs take a long time, because I dig the F in.