- Developers abhor a clean whiteboard
- All code base’s want to have an ICommand abstraction of some sort
- Sooner or later, a project called TestHarness will appear in your source tree
- There will be at least one “The Great Refactoring” episode on the project that you will hence use to date episodes from the project. BDUF all you want, YAGNI all you want, it’s still gonna happen. If it doesn’t, then your code probably sucks.
- At least one grand sounding design idea will generate excitement only to lead to abject failure and disappointment
- At some point you will look at a grand design and suddenly realize a much simpler way to achieve the same goal — but it’s too late
- You’ll do at least one refactoring that makes you walk away and say “I wish we’d done that sooner”
- You’ll do at least one refactoring that makes you walk away and say “Man, I’m glad we did that”
- You will look back at 6 month old code and groan in utter frustration at your lack of ability
- Design strategies that worked well on one project can easily flop on the next project
How I'm using StoryTeller to test FubuMVC
Building a "Lookup" html convention w/ FubuMVC
FubuMVC's Configuration Model "Special Sauce"
Managing Script dependencies with FubuMVC
Authorization and FubuMVC
Composing Views with FubuMVC
Extensible Model Binding with FubuMVC
Modular Packaging with FubuMVC
Self-Installing Apps w/ FubuMVC
Routing and Behavioral Conventions with FubuMVC
What Should I Learn?