I'd definetly go for the framework approach. After building apps with and without frameworks, its a lot less painful to build upon something which exists already. There are so many advantages to go framework, I can't tell everyone: - frameworks are (mostly) under development, so you can benefit from trends and improvements in web development - frameworks are well tested - frameworks are more secure. Do you have all h…
Agreed, a framework is just a toolkit of best practices and useful tools. Another benefit of using a framework is it lets you 'work' with other amazing coders. I have increased my php knowledge many times over by using symfony. Sometimes this happens because you just have to dive into the frameworks sourcecode to see what's going on.
Ask HN: Site from scratch or frameworks?
21–30 of 31 posts
Re: Ask HN: Site from scratch or frameworks?
#22Thanks for clearing this up for me!
Re: Ask HN: Site from scratch or frameworks?
#23Earlier quoted context omitted.
the site is my baby, I want to make a job out of it.(building it from scratch made my skills increase 10 fold). I suppose though, now that its been made, I do have a 'framework' to work with.
Do you want to make a job out of your site, or building a framework for your site? These are two different things, and spending time one one tends to prevent you from spending time on the other.
Re: Ask HN: Site from scratch or frameworks?
#24Re: Ask HN: Site from scratch or frameworks?
#25Earlier quoted context omitted.
Agreed, a framework is just a toolkit of best practices and useful tools. Another benefit of using a framework is it lets you 'work' with other amazing coders. I have increased my php knowledge many times over by using symfony. Sometimes this happens because you just have to dive into the frameworks sourcecode to see what's going on.
It's like having your own personal secretary do all the work and research for you to get the ground work up.. heh I like that analogy
Re: Ask HN: Site from scratch or frameworks?
#26One of the hidden features for a framework, of any sort, is the general understanding of where things are, or can be expected to be. If I work within the conventions of Django, then when I'm hiring somebody, I can ask them if they know Django -- assuming all other things being equal, they'll have a much shorter learning curve ramping up to learn what I've built because they'll know, in general, where to look for certain kinds of things.
If you intend to ever hire anybody, then I'd take every spare minute you have where you aren't coding, and get to documenting the framework you've built.
Re: Ask HN: Site from scratch or frameworks?
#27When you guys discuss frameworks, what exactly are you referencing? I've heard people use that word in reference to languages, CMS', etc... Thanks for clearing this up for me!
Re: Ask HN: Site from scratch or frameworks?
#28Re: Ask HN: Site from scratch or frameworks?
#29Having been through a similar circumstance (built a huge application by myself, which later grew into my job) -- one of the major difficulties you'll have is in finding anybody else that can understand your code. One of the hidden features for a framework, of any sort, is the general understanding of where things are, or can be expected to be. If I work within the conventions of Django, then when I'm hiring somebody,…
Re: Ask HN: Site from scratch or frameworks?
#30I'd definetly go for the framework approach. After building apps with and without frameworks, its a lot less painful to build upon something which exists already. There are so many advantages to go framework, I can't tell everyone: - frameworks are (mostly) under development, so you can benefit from trends and improvements in web development - frameworks are well tested - frameworks are more secure. Do you have all h…