News for hackers. Stuff that matters.
Re:The Code Review Pyramid by owlbite on Tuesday March 22, 2022 @01:04PM (#30768652)
Completely different to the order I use, which basically amounts to "how hard is it to fix this later".

So most important questions are: (1) API must be as correct as possible, especially if its exposed outside of the immediate team. Changing APIs is a royal pain. (2) Documentation of what's going on, especially for non-obvious stuff. If we come back to this in 3 years time and the author has moved on, do we have any hope of fixing it? (3) Testing. What degree of confidence do we have this is doing the right thing? Will it protect me when I change it in a few years time?

Any minor bugs or code style issues can be fixed later as/when they are found and cause problems.

Re:The Code Review Pyramid by greymalik on Tuesday March 22, 2022 @02:48PM (#30769900)
I think you might be misreading the pyramid? The most important things are at the bottom. It aligns exactly with what you’re saying.
Re:The Code Review Pyramid by gunnarmorling on Tuesday March 22, 2022 @03:29PM (#30770377)
Exactly that. "how hard is it to fix this later" is what drives the ordering in the pyramid.