Never create an unknown path in software too? [Toyota principle]

Question

At Toyota's product lines, they always know which path has gone. Just so they can make sure they can fix it, something went wrong. Is this also applicable in software?

All error messages should tell me which path they took. Some make error messages with the stack. Is this the correct interpretation? Can it be used anywhere else?

Ok, here's the podcast. I think it is interesting

http://itc.conversationsnetwork.org/shows/detail3798.html

Answer 1

, . , . , , . , , .

:

, , . , " ", . , , . , ( , ) . , , . , , , , , ( ... , RNG , visual fx). , .

, Bungie , Halo. , . , - , . , .

, . , , , .

Answer 2

. - , . 1000, 1000 ( ).

, .

, , , , , Toyota.

Answer 3

. , . (, , ).

Answer 4

.
, Toyota (-) - , , .. , , , . , , , ...; -)

Answer 5

Google Video " ". () ( ), . ?