I wonder if cashlessness is part of the problem. Counting physical money and counting/checking change helps develop elementary arithmetic skills.
The solution for universities is to force them to learn - give paper exams, no calculator, but with "simple" numbers to have them practice basic math like 0.05mol / 0.5L = 0.1M solution. Make them develop a sense of numbers if they want to pass.
> Intelligence alone won't get us anywhere, or China and Israel would be the best places to live
China: if you are Han, don't care about freedom, social safety net, live upwind from the factories and aren't in the bottom 90% financially, isn't all that bad.
Israel: a very liberal first world western high tech democracy. As long as you're ok dodging incoming rockets on occasion and don't care about religious crap, which most there don't, is pretty good.
China is no different than most developing authoritarian regimes, just bigger.
Israel is no different than most 1st world western countries, except it's run by Jews so obviously it's a bad place.
They made db change. They have effectively infinite amounts of real production flow data they can use to test changes.
In this case, the system failed because it was hard coded to 200 max tests but they added more. If they had tested against that it would've been found.
This is not an obscure rarely used feature. This is a key feature of what their entire service is built around. They are selling filtered/clean incoming traffic against very large production sites. Who thought it was a good idea to have a hard cap of how many rules could be applied in the first place?
This is very much "no one will ever need more than 640k" thinking.
The closest I've ever got to doing similar was using a numeric incremental dns naming scheme based on 3 or 4 digit names like web001-999 or service0001-9999 knowing that it wouldn't be a surprise if we ever ran out of names, especially considering we had a dozen servers at the time which could easily handle 50x the current traffic load. But a numeric naming scheme isn't a surprise when you run out. Long before that we changed to "datacenter-service-number" so web005 became dc3-web-005 giving us up to 1000 web servers per data center in data centers that didn't have space for another 1000 servers anyway.
But this secret hard coded db limit is simple incompetence and lack of real world experience.
Again, this is the very core of their business model. Yet no one knew anything about how their systems work. It wasn't a complex problem. It was a dumb hard coded cap.
I have also seen very complex systems collapse under their own weight. This was not one of those times.
Seriously?
Even most of the shitty under resourced startups I was at had basic dev -> qa -> staging -> production environment life cycles in place.
This sort of failure is a result of sheer incompetence, bad systems engineering, and clueless management at all levels.
Outages? Yes, shit happens.
Preventable outages by huge critical infrastructure company in their key systems? Clown show.
Her wife was giving him the cold shoulder.
I have the simplest tastes. I am always satisfied with the best. -- Oscar Wilde