Hacker News new | past | comments | ask | show | jobs | submit login

I meant it's fine to take calculated risks.

E. g. we have less than 1% chance per year that a given person leaves us on bad terms or suffers a bad accident or illness. In case it really happens, it will cost us X in delays and extra work. To lower the probability of this risk to Y% would cost us Z (money, delay, etc).

If you do this math, you can tell if it's a good idea to optimize here, or if you have more pressing issues.

In my experience, this sort of one-man jobs gets automated or at least well described and checked for fear of mistakes and/or employee fraud rather than "downtime".




Mistakes are "downtime" as well in a way. Or maybe better, downtime is a mistake, cause errors and lead to problems.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: