Coming from the FP perspecitve, I think a useful way is to see things in terms of striking a balance between "knowing the value of everything and the cost of n

Coming from the FP perspecitve, I think a useful way is to see things in terms of striking a balance between "knowing the value of everything and the cost of nothing" and "knowing the cost of everything and the value of nothing" and it is extremely context-sensitive esp with respect to the team of people making the software. As humans we tend to forget that programmers are ultimately just machines that turn coffee into reads and writes = )