Got fired on my last job saying this. Such a shame I don't have a PhD like their CSS coder. My understanding of the root causes of the time problem is a poor e

Got fired on my last job saying this. Such a shame I don't have a PhD like their CSS coder. My understanding of the root causes of the time problem is a poor education. Basic definition of time : time is the accident of the accident, and the same causes giving the same effects, some of them being irreversible they define an ordered direction of events. Time is like temperature, it is measured relatively to the pulsation of an harmonic oscillator. A closed absolute system time does not exists. Since Einstein we also have to decorrelate the physical speed to the speed due to the geometrical expansion. (Cerenkov effect, yes you can go faster than the speed of light playing on this). Since quantum mechanics we know time is quantic and its uncertain capped by hbar/2 < dEdt Hence a lot of problem when due to poor rigor and understanding (which amplify the aforementioned effect) time becomes that its nightmarish physical beast. And you are stuck with idiots, that even thinks that the colour of the skin influence your quality as a coder. So here is my understanding of coder's problem with time. The mindset of coders I have met and boss alike is stuck in the 1800's. Where statistical physic, the dual nature of light, quantum mechanics, Einstein's relativity are known as trivial pursuit boring questions but no one cares of the implications. Then they sux at understanding geometry vs physics but most of all they are stuck in the wrong physical world. They live in a world of determinism where they would prefer compute the position and speed of every molecule in a gas than use the 'unpure' perfect law. For time they are puzzled: - time is a length of vector; (how much time since) - time is a point - deducted from an implicit 0 origin when taking a length; - time is 1D vector so it behaves like a scalar, so it must be a scalar; (computing resulting size by adding/substracting as length/vector)) - there is a lot of politic involved in "time measure" (GMT, TZ, calendars, interstitial seconds) and politic is buggy thus it results in bugs; - heisenberg DOES exists; they never care to measure the error and think it is wasted time; - my time as a coder is always free; - time cannot be uncertain since we have these high resolution clocks (the exactitude of time is such we never encounter uncertainty (and our code is executed in 0s))); - GPS is a measuring instrument that magically corrects this, because it is perfect and has no errors because it is USA spatial "godly" "star streky" in the sky; - acausality cannot locally happen because of asymmetries in topologies (slow/fast router vs short long path); In short, most of coders are insanely crippled by their own culture of ignorance and their self importance. Common scientifical knowledge that is more commonly understood by mc donalds employees has still not reached the brain of our elite architects/coders. And time - frequencies is one of the most important dimension of all applications. The question I wonder is "how?". How is it even possible to have such a bias in the mass recruitment of coders that they select over confident thinkers that are lacking of curiosity so much they can blindfold themselves comfortably. If the lack in scientific domain is that great, and reflects arrogant lacks in other domain ... then I think of creeping lack of culture in "business", "ethics", "legal", "cryptography", "probability", "algebrae" ... I have provoked enough computer pro and made stats to know for sure their level of confidence should be dangerously inversely correlated to their level of actual knowledge. I am very confident that IT has a corporate culture bias of valuating arrogant ignorant that "can do it" over careful thinkers that may say "it well never be doable"* * yes, the Cretan paradox revisited