05-18-2009, 01:12 PM
|
#24 (permalink)
|
|
The Gregarious
Join Date: Feb 2009
Location: New York
Posts: 645
Thanks: 64
|
Quote:
Originally Posted by Wildhoney
I really wouldn't use my own custom method. I've tried to do projects where I've maintained my own framework, if I were maintaining my own data storage as well, I'd have collapsed and quite likely have died by now.
Don't, just don't  Not if you know what's good for you! Use something that's been around for a while, it's been tested throughout. The less work you give yourself in management, the better. I don't even manage my own framework any more.
Being young programmers though, we do like to think we can manage it all. |
Agreed. I think what it comes down to are 3 things.
1) reluctance to use a DB, hence the need to go flat file. Which now you have to come up with a whole way of accessing/modifying the file in your own custom way which is not a guarantee any success.
2) advanced programmers have already been there done that, so it's quite easy for them to see the positives of using a framework to avoid re-inventing the wheel.
3) curiosity. I personally need to re-invent the wheel so that I can have a better understanding of how things works before I start to fully engage in frameworks etc...plus it would also allow me to appreciate frameworks. |
|
|
|