3 ms·

> When you have a website to build, you reach for an existing web framework, because it has already done the bottom-up steps for you. As I see it, it is from b

• alexashka 8y ago
  I agree with you, the frameworks/libraries have done the bottom-up for you, to say, 70-80%. The other 20%, you need to work out on your own. The final 20-30% are really marrying the exact business needs, with the underlying libraries/frameworks you're using. The smaller the % of work needed to marry the business needs with the libraries, the more it starts to look like an application, like Photoshop, and less like programming.
• wvenable 8y ago
  Almost everyone should build their own framework on top of existing frameworks for their own domain. At work, we have a common look and feel for all our applications so that's build into the framework. We have specific domain specific data types -- those would never go into someone else's generic framework but they are in ours. I find this idea of building your own framework to be pretty rare -- I do it because I've actually had to build frameworks for platforms that didn't have them -- but most programmers are content to use what they're given but never think of extending it.