4 ms·

I'm a big fan of the "build a framework that you'll never use" philosophy. That isn't a joke. You aren't going to be able to match the quality of the thousand

by mdasen 18y ago

I'm a big fan of the "build a framework that you'll never use" philosophy. That isn't a joke. You aren't going to be able to match the quality of the thousands upon thousands of hours that have gone into something like Django, but making a framework will make you a better framework user. It makes you understand the flow, what building hooks is like, etc. It also means that you'll be more ready to dive into some of the framework code than someone who just uses a framework. But that's just my opinion from seeing so many people not understand how frameworks work and try to use them.

icey 18y ago
I agree with you on this, but only if you already know how to write good code. If you're learning how to develop first (or re-learning) I think that it's a road that's going to be paved with frustration.
markbao 18y ago
I second this notion. Also, unless if you really, really think it is good for production use, regard the last part as well. Don't use it. I built a framework that was pretty decent, learned a lot about not just the language but also the framework and the MVC pattern, used it in production and it bit me in the ass later. Why? It wasn't good enough. If you're going go use it, make sure the framework you build isn't decent but excellent, and I'm only saying this because there are people who have written great frameworks before. The problem is that you might get caught up in your own "but I built this so it must kick ass" like I kind of did. Doing so is like using a software package from a sketchy vendor (no offense) and you wouldn't do that, would you?
ashleyw 18y ago
I agree, but I also think using a framework is just as good in the long run... You basically have hundreds if not thousands of people working on your project with you, fixing bugs, making it faster, more stable, and adding under the hood features. Something you would need to do yourself if you created your own framework.
wheels 18y ago
I think building a framework is an important rite of passage for serious developers, but not at the point that the poster seems to be at. I think you have to know what you don't like in existing frameworks, and have ... I hesitate to use the phrase ... a vision ... for it to be a meaningful experience.

by mdasen 18y ago

icey 18y ago

I agree with you on this, but only if you already know how to write good code. If you're learning how to develop first (or re-learning) I think that it's a road that's going to be paved with frustration.

markbao 18y ago

I second this notion. Also, unless if you really, really think it is good for production use, regard the last part as well. Don't use it. I built a framework that was pretty decent, learned a lot about not just the language but also the framework and the MVC pattern, used it in production and it bit me in the ass later. Why? It wasn't good enough. If you're going go use it, make sure the framework you build isn't decent but excellent, and I'm only saying this because there are people who have written great frameworks before. The problem is that you might get caught up in your own "but I built this so it must kick ass" like I kind of did. Doing so is like using a software package from a sketchy vendor (no offense) and you wouldn't do that, would you?

ashleyw 18y ago

I agree, but I also think using a framework is just as good in the long run... You basically have hundreds if not thousands of people working on your project with you, fixing bugs, making it faster, more stable, and adding under the hood features. Something you would need to do yourself if you created your own framework.

wheels 18y ago

I think building a framework is an important rite of passage for serious developers, but not at the point that the poster seems to be at. I think you have to know what you don't like in existing frameworks, and have ... I hesitate to use the phrase ... a vision ... for it to be a meaningful experience.