I would like to ask something about project management. I got a project that has
ID: 650982 • Letter: I
Question
I would like to ask something about project management. I got a project that has some requirements, it can be done from scratch with the use of a big framework. Maybe some tools are necessary for some of the functions. But using a framework seems very cool, it seems that reduces the amount of work, but need to study a framework first. But study a frameworks seems very big for the team. So, what do you think? Just get the thing done from scratch or study a framework and get started like 'Standing on the shoulders of giants'?
Explanation / Answer
If wheels were never reinvented for good reason, Honda Civics would have wheels chiseled from stone.
One great reason to not use a framework is that a lot of frameworks suck so bad, light barely escapes them. Sadly, people who use nothing but frameworks and libraries tend to not be in a great position to evaluate them.
As a client-side web dev, I've learned to favor tools that help you get the job done fast without compromising the flexibility you get from doing things your way because the tools will stay out of your way when you need them to. Django and JQuery (not really a framework technically but fits with the discussion) are very much built on this principle. Both are also stupid popular with those of us who continue to want more granular control of how stuff is implemented.
The prefab collectoins of built-for-you stuff, particularly where UI is concerned are almost never as flexible as you wish they had been and good luck to you when you want to start customizing something. I'm not saying you shouldn't shop around, but if you know your stuff and the available tools seem kind of awkward and difficult to maintain, ditch 'em and DIY. You will save time in the long run.
But the critical thing to remember is that you can almost always have your cake and eat it too. If you're trying a new framework or library out and it seems full of unnecessary chains of dependencies and requires overly rigid implementation that puts pointless constraints on environments it lives in, toss it out. It's a bad tool.