loading...

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

FULL DISCUSSION
 

IMHO,

if you work alone, yes you don't need to use any framework. Build up your basic first and as long it works, don't give bug, and the client satisfies with it, it is ok.

but if you work with a team, you need a standard structure for people to working together. for me, that is the point of having a framework.

I have been in a company that doesn't really use a framework, any framework, they just hate it when I mention about changing their development method from vanilla to framework. The manager will look at me like he will kill me if I mention any framework.

oh heck, the even don't use OOP approach.

for 8 years, it is pain in the a**.

 

but if you work with a team, you need a standard structure for people to working together. for me, that is the point of having a framework.

Have you tried talking and collaborating with your team? Is it really neccessary for a framework to enforce a collective sense of what software should look like?

 

It isn't necessary, it just costs time to roll-you-own. Which means money (salary mostly) and opportunity (time-to-market mostly).

When you use an existing framework you save time in at least these areas:

  • Writing documentation and keeping it up to date
  • Getting a new hire up-to-speed
  • Implementing new features
  • Guarding against security vulnerabilities^
  • Getting answers to questions without costing the time of a teammate

^ Security is a big one, Rails for example has a bounty program for finding and reporting vulnerabilities. Is your team paying someone to find security vulnerabilities so you can patch them before they are exploited?

code of conduct - report abuse