It reminds me to a tweet I saw few weeks ago, when NASAs satellite reached Pluto: NASA: sent a probe to Pluto 9 years go. Reached its destination without problems, with 72 seconds of arrival estimation error Me: press F5. Undefined is not an function.
Then it reminds me to a law of leaky abstraction: the app we're building sits on top of dozens and dozens of abstraction layers, and by pure statistics something will go wrong, some crazy edge use case will magically appear.
Putting that into a context of a web app, where you get several hits per second, chances of 100,000 that something will go wrong, some unpredicted and unexpected user input will find a hole in you validation logic, means basically next Thursday. Good thing I'm not building navigation system for Pluto probe, thats all I can say, or else Huston would receive radio signal saying "undefined is not an function" after 9 year space flight;)
It reminds me to a tweet I saw few weeks ago, when NASAs satellite reached Pluto:
NASA: sent a probe to Pluto 9 years go. Reached its destination without problems, with 72 seconds of arrival estimation error
Me: press F5. Undefined is not an function.
Then it reminds me to a law of leaky abstraction: the app we're building sits on top of dozens and dozens of abstraction layers, and by pure statistics something will go wrong, some crazy edge use case will magically appear.
Putting that into a context of a web app, where you get several hits per second, chances of 100,000 that something will go wrong, some unpredicted and unexpected user input will find a hole in you validation logic, means basically next Thursday.
Good thing I'm not building navigation system for Pluto probe, thats all I can say, or else Huston would receive radio signal saying "undefined is not an function" after 9 year space flight;)