About the Talk
January 22, 2013 7:00 AM
Topeka, KS Dot Net User GroupTopeka, KS Dot Net User Group
Inspired by Steve McConnel’s “Code Complete”, Uncle Bob’s “Clean Code” and Andrew Hunt’s “The Pragmatic Programmer”, this session discusses best practices for writing code in a style that’s easy to create, maintain and understand. We have a lofty goal: programming style as documentation. We’ll discuss concrete methods to get you there and give you a vocabulary for pragmatically evaluating code quality.
Various refactoring techniques, code smells, anti-patterns, and rules of thumb are discussed including fail fast, return early, separation of concerns, arrow code, magic numbers, the boy scout rule, being “stringly typed”, DRY, the stepdown rule, table-driven methods, the importance of staying native, techniques for finding subtle redundancy, reinventing the square wheel, when to create a method, doing comments right, horizontal and vertical density, and simple design patterns. Part of this session involves refactoring a confusing and ugly chunk of code into something beautiful, easy to read and maintain. While examples are in C#, coders in any language should be able to follow along and apply the principles discussed.