Re:Reading Other People's Code (2012)
by gnaritas on Wednesday September 04, 2013 @03:51PM
(#6330001)
> So the only way I can understand what the code is doing is by stepping through it in a debugger.
If methods are factored and named well, the name tells you what it does and you shouldn't have to look at the implementation unless its not doing what it says.
I've found that good OO programs are understood by understanding the classes and messages between them, not by reading the implementations of those methods. Look for the big picture, not the details.
If methods are factored and named well, the name tells you what it does and you shouldn't have to look at the implementation unless its not doing what it says.
I've found that good OO programs are understood by understanding the classes and messages between them, not by reading the implementations of those methods. Look for the big picture, not the details.