Based on this observation and the literal wasteland of half baked frameworks available, I’m sharing some insight on how to design a useful framework. Follow these rules and you’ll have a higher probability of having something useful, ignore them, and well…I guess that’s your choice, I won’t hate you for it (OK, maybe I will a little).
Step One: Pick an existing framework
No, this is not a tongue-in-cheek joke, this is reality. Unless you initially demonstrated your framework at Bar Camp back in 2006, you should start with something that already exists and first deliver your project with that.
Step Two: Find things that the chosen framework doesn’t do well
Now look at your product that is “code complete” and do an analysis of where your most common bugs happen, where new developers trip up and make mistakes, or where the code is repetitive. If nothing stands out…STOP, you’re done. If there are rough edges, analyze approaches to the rough edges, and see how other EXISTING frameworks solve the problem. If nobody’s solved it or if you think you’ve found a better way, refactor your code and enhance your chosen existing framework.
Step Three: After doing this for 4 to 5 years, and you’ve found better patterns or something novel, write a framework
Note, this step seems to be the one everyone skips (even authors of currently popular frameworks). Experience is important, attempting to write a framework after doing a “TODO” list app because you discovered something you don’t like is a recipe for disaster. Moreover cross posting your new framework announcement across the internet to “make a name for yourself” is irritating and counterproductive.
Step Four: Write some useful applications using your framework
I don’t mean to discourage creativity, and still encourage folks to experiment and try things out…but temper your enthusiasm with reality until you can clearly illustrate how your new framework is better. In addition, be sure to look at your baby objectively…warts and all.