4 ms·
But unless that 3rd party code, and those services, have already been discovered, evaluated, and learned by that particular dev team, integrating them might tak
by danaris 3y ago
But unless that 3rd party code, and those services, have already been discovered, evaluated, and learned by that particular dev team, integrating them might take more time than building something from scratch that meets the specific requirements at hand.
And if it's built in-house, that means that in addition to being much more tailored to the organization's needs, it can be much more easily changed as those needs evolve.
This doesn't mean that I think it's always better to roll your own, of course; there are lots of instances where that counts as "reinventing the wheel." But it's absolutely not as simple as "just use something that's already out there and it will be faster and work just as well."
- tyingq 3y agoI wasn't suggesting that example was a magic bullet. Just that it is one of many choices that drive an estimate...down OR up. I agree there are cases where 3rd party software doesn't help. I think it would be pretty rare for a team to have zero choices in their control that would change an estimate.
- jeltz 3y agoQuite often using third party tools take longer time but still are worth it in the long term due yo lower maintaisnce and generally simpler tech stack.