I’m inclined to agree. “Give a man a fish; you have fed him for today. Teach a man to fish; and you have fed him for a lifetime.”
“Why reinvent the wheel?” you may well ask. That’s a fair point as long as you’re happy about never understanding how wheels work. Lord help you if ever get a flat tyre.
I’ll admit that I’m personally a bit of a control freak. I get very uncomfortable with the thought of any third party meddling with my code. That’s why I’ve always been very wary of (so called) WYSIWYG editors.
I like a big set of tools available to call upon at need, I like to have a favorite hammer and a favorite saw and know the tricks for making them both fit on my belt without running into my legs when I am working on something. Framework people like the 5-in-1 lathe-press-drill-saw-grinder and figuring out the tricks to fit the piece of wood they are working on into the machine. When you have a framework everything will be lathe-press-drill-saw-grinded into submission, and you better read the manual otherwise the machine won’t even turn on.
He’s got a point. Sometimes the frameworks themselves have such a steep learning curve that you’d be as well off just figuring out how to write your own solution.
So my advice is the same as Dustin’s: learn the language first. If you then want to use a framework and you understand how and why it works, then by all means do so. If you don’t understand the inner workings, then you run the risk of becoming a cargo-cult programmer.
Posted by Jeremy on Wednesday, November 16th, 2005 at 4:40am