3 ms·
Sometimes, though I suspect in a lot of cases that's probably for the best. I mean, if a product or service exists and does what you need it to, isn't it better
by CM30 9y ago
Sometimes, though I suspect in a lot of cases that's probably for the best. I mean, if a product or service exists and does what you need it to, isn't it better to take advantage of that rather than reinvent the wheel every time? Sure, you could create your own inhouse CMS for those client websites or what not, but it's likely not worth it given the effort of making your updates, fixing security holes, etc. Same with anything really. You could in theory try and go all the way back to the start on your own, but where does it end? Eventually you'll be doing ten times more work for little extra benefit.
Are there examples where doing the extra work could be better? Of course, I know that one from experience. All that time trying to integrate a CMS and a forum script and a bunch of other standalone things was a nightmare, and in that case I definitely wish I'd just rolled the whole thing myself instead.
But in many cases, it's probably better to use pre-existing solutions rather than spend all your time reinventing the wheel or falling victim to not invented here syndrome. That way, you're relying on well tested solutions with a decent amount of support available online and a guarantee it'll still work when most of your team has moved on to pastures new.