I'm also not a fan of quantifying productivity lost in ££. When someone has a bowl movement do you chart that against company productivity?
We have a sysadmin who looks after the servers. However, bad things can happen. If he was able to spend all his time working on these problems, they wouldn't occur, but he has other responsibilities too. Should we hire someone else? No! It's cheaper and more reliable to outsource these responsibilities to a team working 100% of the time on it.
> I'm also not a fan of quantifying productivity lost in ££. When someone has a bowl movement do you chart that against company productivity?
I don't understand your point. There's a big difference between going to get coffee, go to the toilet, etc - which is normal, expected and accounted for - and having large parts of the company unable to work because particular services are down.
Well if he did a good job it would be adequately mitigated. This isn't 1997. It is trivial and cheap to set up reliable redundant systems. Outages happen. But not very often if you have done your job half right. Hopefully so rarely that you decay to near zero.
> and having large parts of the company unable to work because particular services are down.
If it was real time critical yes. But tis a distributed VC we are talking about. Just wait 15 minutes to push and spin your build to the customer. It isnt the end of the world.
Not doing it yourself may mean going with BitBucket for some or all of your private repos, in this case.