The sad part is a lot of people have timing problems, they just don't recognize them.
Any time you have spurious or intermittant problems, they are most likely caused by timing issues. I have tried to get people to do a timing analysis of each thread at the system level, but most just say its not a problem and go on.
Timing errors can waste a tremendous number of testing hours, plus they really make users angry when the software behaves erratically.
Software is more than just an App! It represents a controlled method for executing a process within a system environment. The environment can be a smart phone, washing machine, scientific satellite, car, or any of the billion of computer controlled devices now in use world wide. Timing is every bit as important as chosing the right processor, bus speed, storage or any of the other system components. If the timing does not work, one or all of the other components become useless.
In short, if you do not conduct a timing analysis, then you have a potential vulnerability in your system. If you care at all about the quality of the work you do, then you need to make sure that your application works under all types of conditions and has a prepared method to deal with the system degridation brought on by timing issues.