Saturday, October 3, 2009

12 Practices to be a Better Developer

The 12 Practices

  1. Source Control - If you don’t store your code in source control, you’re putting your company at risk.
  2. Test-Driven Development produces higher-quality code. Behavior Driven Design - Behavior is documentation for other developers and users.
  3. Build Systems - Building is more than just compiling code.
  4. Continuous Integration - Check in early and often.
  5. Real Time Code Review - Two heads are better than one.
  6. Refactoring: Easy as red light green light.
  7. Read Code - "You don’t become a better writer by just writing." Scott Hanselman
  8. Code In Increments - Real programmers work for hours and hours straight, without a break, without even looking up. Don’t break your flow to stop and compile: just keep typing! :)
  9. Sharpen your skills by learning a new language.
  10. Learn SOLID
    • Single Responsibility Principle - There should never be more than one reason for a class to change.
    • Open Closed Principle - A class should be open for extension but closed for modification.
    • Liscov Substitution Principle - Subtypes must be substitutable for their base types.
    • Interface Segregation Principle - Clients should not be forced to depend upon interfaces that they do not use.
    • Dependency Inversion Principle - High level modules should not depend upon low level modules. Both should depend upon abstractions. Abstractions should not depend upon details. Details should depend upon abstractions.
  11. Know when to unlearn. The ways you learned when you first started are clearly the best ways. Not much has changed since then, really. :)
  12. Be a Mentor

Read further here: 12 Practices to be a Better Developer

No comments: