The title says it all really.
What materials have you read (or in another way learned from) that make you a better reviewer?
1 item per answer please - let the good ones get the votes ;-)
|
The title says it all really. What materials have you read (or in another way learned from) that make you a better reviewer? 1 item per answer please - let the good ones get the votes ;-) |
|||||||||||||
|
Questions on Code Review Stack Exchange are expected to relate to code review request within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.
|
|
|||||||||
|
|
I'm amazed this one hasn't been mentioned yet. Anyone doing any software development should read this: Design Patterns: Elements of Reusable Object Oriented Software
|
||||
|
Programmers.StackExchange (which is also where this question should be posted) |
||||
|
|
|
I would add to the list
Then again, I'd imagine SO already has a pretty comprehensive book listing on this subject |
||||
|
|
Definitely without a doubt a website called Refactor my Code. It's not something you can physically read, but in relation to code reviewing, it can sometimes be a big help. |
||||
|
|
|
Facts and Fallacies of software engineering: http://www.amazon.ca/Facts-Fallacies-Software-Engineering-Robert/dp/0321117425 |
|||||||||
|
|
I've found this useful in getting some tidbits from others in the field: Programming Pearls |
||||
|
|
|
C++ specific, but still an excellent resource: Effective C++ |
||||
|
|
|
AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis: http://www.amazon.com/AntiPatterns-Refactoring-Software-Architectures-Projects/dp/0471197130/ref=sr_1_1?ie=UTF8&qid=1295490014&sr=8-1 |
||||
|
|
|
Code Quality: The Open Source Perspective
I found Code Quality, the Open Source Perspective and impressive book. Analysing common openSource Projects, it shows bad habbits etc. |
||||
|
|
|
A very good site to show what bad code looks like (among other things): (also very good for a laugh - and yes I'm serious, this is a good resource for learning about code quality) |
||||
|
|
|
Take a look at this book as well... I.M. Wright's "Hard Code" Eric Brechner http://oreilly.com/catalog/9780735624351 |
||||
|
|