Anti-Patterns and Worst Practices

Writing C# is one thing, but writing it well is a combination of many things. Not only will this tell you which traps to avoid, but why you should avoid them. Great concepts for beginners and good reminders for even the most seasoned coders.

From the Trenches

Chris will be the first to admit that he has written some really awful code in his past. He's still not done writing bad code, but he does have a radar for it now. Over the years he has fine-tuned his senses to be able to spot some bad code. His connections in the community have always been there to help him understand why it's bad code. It's now time for that knowledge to be shared.

Well Traveled

Chris has put his time in with enterprise software, e-commerce, consulting firms, the open source community, and start-ups. He has been around the block a time or two. Code can look great in one community and come off as completely worthless in another. There's always context, deadlines, and expectations to define this quality, but there are also ways to develop in such a way that make these environmental factors irrelevant.

Table of Contents (pending)

1. Introduction
   • Why write this?
   • Love it or Hate it, You Want Good Code
2. Who cares? It works!
   • Why is good, clean code important?
   • Be kind, rewind
3. Rookie Mistakes
   • Your Code is Doing Too Much
   • The Arrowhead Antipattern
   • The Monster Object
   • Utils, Managers, Helpers, Oh My!
   • Patterns to Help You
4. Overdoing It
   • Don't Reinvent the Wheel
   • You Aren't Better or Faster than the BCL
   • Don't Abuse the Language, Use the Language
   • Patterns Aren't Prescriptions, They're Guidelines
5. What's Next?
   • The Vision
   • The Tools