re: Why You Shouldn't Use A Web Framework VIEW POST

re: Solve your client's problem ... Start with a framework to abstract alot of the implementation, then evolve over time

Ummm... why not solve the problem, then extract a framework if it looks like you've built one.

Which I don't think you will. Unless you're DHH.


Oh yes indeed, what I have learnt is that most problems have been solved - so I need to build on top of that as I do not have the time

Rather than extract and drive my own framework, better to contribute my existing problem approach to another framework that solves a similar problem.

code of conduct - report abuse