2 ms·
From my experience so far, I'd rather inherit an in-house solution to something than a hacked-in didn't-exactly-meet-the-requirements-in-the-first-place third p
by majormajor 12y ago
From my experience so far, I'd rather inherit an in-house solution to something than a hacked-in didn't-exactly-meet-the-requirements-in-the-first-place third party library. I find the latter cases particularly painful to keep running well when the need to update the original project comes along.
If you're going to pick a third party library, try to make sure you can depend on it to be supported for as long as your project will be. Otherwise it's not much different than inheriting code that's not supported because the original author left the company.
The built-in-house solution tends to have less useless-to-me stuff bolted on in an attempt to be "versatile" but that ends up getting in the way down the line. (This is hardly universally true, though: the built-in-house swiss-army-knife attempt is probably the worst of all worlds.)