Code Review Best Practices

Re:Code Review Best Practices by krzyk on Sunday May 10, 2015 @02:06AM (#9519032)

If you name the methods correctly (what they do) splitting actually helps readability of the code. It is quite hard to read and remember what was in the beginning of 500 line method.

[ Parent | on HN ]

Re:Code Review Best Practices by AlisdairO on Sunday May 10, 2015 @05:42AM (#9519426)

IE it can help to understand the intent and flow of the code, but also make it harder to debug. If I'm in a situation where I want to follow the exact instructions a large fraction of the code performs, a call stack jumping all over the place can be pretty frustrating.

[ Parent | on HN ]

Re:Code Review Best Practices by motti on Sunday May 10, 2015 @04:56PM (#9521287)

Step over

[ Parent | on HN ]

Re:Code Review Best Practices by AlisdairO on Monday May 11, 2015 @06:02AM (#9523600)

...doesn't help if I want to actually see what code is getting run

[ Parent | on HN ]