Mapreader4’s Reviews > Clean Code: A Handbook of Agile Software Craftsmanship > Status Update

summary of chapter 3: functions should do one thing, and *only that thing.* they should be short and have a short list of arguments. try to avoid nested loops and if statements. avoid output arguments and error codes in favor of standard OOP features. your code will not look like this on the first try; therefore, write a first draft, then revise.

summary: choose names to include as much signal and as little noise as possible.