3 ms·
> Buy Almost Always Beats Build The devil is in the "Almost". I agree 99.9% with the examples the author chose (db, k8s -- if you even really need it). But a
by gumby 6y ago
> Buy Almost Always Beats Build
The devil is in the "Almost". I agree 99.9% with the examples the author chose (db, k8s -- if you even really need it).
But a lot of third party code is rife with gotchas -- often excellent as development scaffolding but risky in deployment. npm is notorious in this regard.
What does "buy" buy you? 1 - hopefully a lot of people are using the code in question so it will have fewer bugs. 2 - hopefully time to deployment
But in exchange you may be using a piece of software that might be robust in domain X but not in yours. You're signing on to a piece of code that may be excessively general for you, or inversely make assumptions that shoehorn you down an inconvenient path.
And of course now you're on someone else's config and development timeline.
So it's a balance like any other.
- hliyan 6y agoSometimes you need to buy and integrate three different tools to get the thing you could do with a small in-house tool. And each of those three tools have a lot more features and options than you need and require a lot of configuration. Then you also have to upgrade those tools. Sometimes you need specialists. Sometimes if something breaks due to an upgrade you have to contend with the vendor's support staff. Sometimes, all you needed was 50 lines of bash script.