Viewing By Entry / Main
February 17, 2007
Brian Rinaldi has a great post about stalling on choosing a framework. I've heard several of the arguments he quotes against using frameworks - in fact, I recently provided a very similar answer (to Brian's) on a mailing list, when a user group manager said they were getting questions from their members about this issue.
The important part is using a framework, not so much which framework. Just pick one...
Comments
Ha! It's the same thing with processes, methodologies, bug trackers, version control, project management apps...
Some infrastructure is always better than none. Once you have something in place, you're always better equipped to make changes.
At some point, waffling about which one is best becomes just that... waffling.
This, of course, isn't unique to frameworks. The advice applies to any uneducated- or less-than-educated choice that's going to be made.
Unless one choice offers a compelling reason to choose it, choose any one and get started. Learning how stuff works within that choice is educational and will help guide future decisions of the same nature - if any need to be made. At some point, the search for some divine sign to pick one over the other simply becomes paralyzing, in my experience.
Post Your Comments
Hosting provided by
