Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I suspect what he means is that the “root cause” is not a single, binary thing that is simply “fixed or not fixed”.

In the training example, it’s quite possible that the first hour of training will cover 80% of the problem, with subsequent hours offering diminishing returns. The point is to discover it while avoiding waste.

He’s acknowledging that “root cause” is a club that can be used for bureaucracy; handled wrongly it looks a lot like premature optimization or CYA. What he’s describing is what I consider empiricism.



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

Search: