4 ms·
>Do I use frameworks? Only when it's not required to maintain a product in future. I've been on the flip side of this too many times. Some outsourcing company
by fsk 12y ago
>Do I use frameworks? Only when it's not required to maintain a product in future.
I've been on the flip side of this too many times. Some outsourcing company developed a product using a framework (usually on a fixed-price bid), which enabled them to ship something that sort of mostly worked so they could get paid. Then, I'm stuck supporting and maintaining it, and it takes 3x-5x longer than it should because of the poor framework choice and poor usage of that framework.
- a_c_s 12y agoI've been there a couple of times, dealing with abused frameworks can be rather painful! However, I think the big problem is dealing with code that an outsourcing company "sort of mostly worked so they could get paid". The incentives are just not there for a quality product: framework or not, they are going to produce a slapdash hodgepodge of code. If they didn't have a framework, is there a reason I'm not seeing to think that the resulting mess of code would be any easier to support?