Home
Building Maintainable Software, C# Edition: Ten Guidelines for Future-Proof Code
Loading Inventory...
Barnes and Noble
Building Maintainable Software, C# Edition: Ten Guidelines for Future-Proof Code
Current price: $24.99
Barnes and Noble
Building Maintainable Software, C# Edition: Ten Guidelines for Future-Proof Code
Current price: $24.99
Loading Inventory...
Size: Paperback
*Product Information may vary - to confirm product availability, pricing, and additional information please contact Barnes and Noble
Have you ever felt frustrated working with someone else’s code? Difficult-to-maintain source code is a big problem in software development today, leading to costly delays and defects. Be part of the solution. With this practical book, you’ll learn 10 easy-to-follow guidelines for delivering C# software that’s easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems.
Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in C#, while our companion Java book provides clear examples in that language.
Write short units of code: limit the length of methods and constructors
Write simple units of code: limit the number of branch points per method
Write code once, rather than risk copying buggy code
Keep unit interfaces small by extracting parameters into objects
Separate concerns to avoid building large classes
Couple architecture components loosely
Balance the number and size of top-level components in your code
Keep your codebase as small as possible
Automate tests for your codebase
Write clean code, avoiding "code smells" that indicate deeper problems
Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in C#, while our companion Java book provides clear examples in that language.
Write short units of code: limit the length of methods and constructors
Write simple units of code: limit the number of branch points per method
Write code once, rather than risk copying buggy code
Keep unit interfaces small by extracting parameters into objects
Separate concerns to avoid building large classes
Couple architecture components loosely
Balance the number and size of top-level components in your code
Keep your codebase as small as possible
Automate tests for your codebase
Write clean code, avoiding "code smells" that indicate deeper problems