> Thinking, you build it, you run it, will work in the long term This is basically the "hit-by-a-bus" scenario and it applies to pretty much anything in which

> Thinking, you build it, you run it, will work in the long term This is basically the "hit-by-a-bus" scenario and it applies to pretty much anything in which you have a single point of failure in terms of manpower, not just in-house software. e.g. What happens when the engineer who installed your open-source solutions leaves? Who is left to support updates, migrations, etc? The solution to this is of course is to staff correctly...so that you don't have a single engineer building out an entire code base or system that your company heavily relies on.