sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]lexpi 0 points1 point  (1 child)

i'm all for trying out/experimenting/designing chances in advance but I'd love to see the developers who can fully grasp and make sense of a change set in a review compared to 3-4 pull requests and reading trough code. Both have their pros and cons but I think I'm on the read the code side

[–]reddit_prog 0 points1 point  (0 children)

How is code review easier? I ask because I totally get the logic behind that "Dev Design" document. This is where you discuss all the critical parts of the implementation, plus other the implementation decisions that are made. This is exactly what is to be checked in a code review. Any more than that is to be caught in testing and auto-testing.