> I wonder if it's possible to learn that decisiveness.
If the culture allows for it, yes.
On final my instructor was talking about the next approach. I heard the words 'go around' and immediately executed one. He realized that (1) that conversation was unnecessary at that phase of the flight and (2) to not use those words unless he wants me to immediately go around :)
After soloing, I sometimes report that I had to go around because I didn't like how the approach or landing was looking like. I got praised for it every time.
> I don't know anything about flying. Is this normal?
Not deploying thrust reversers is normal, not all situations require them. But brakes are terrible when the wings are still flying, so spoilers (if armed as they should) automatically deploy when all wheel sensors report the aircraft is on the ground, so that there will be more weight on the wheels and the brakes can work properly.
This should not be the case for any modern airline; too many accidents were caused by exactly this problem in the past.
However, I don't doubt shady operations might be doing this(more so if they aren't carrying passengers). They won't be around for long if they are caught doing this kind of nonsense and it causes an incident (or accident in this case).
Today there may be some rules (more than X go arounds because of weather, you have to divert, etc).
If there is a company willing to bend rules to increase profits, I'd bet it'd be Amazon's retail side. Not via explicit punishment, because that'd be too easy to catch, but bonuses for timely arrivals, fuel efficiency, and so on.
Well they tend to optimize heavily by discouraging things like bathroom breaks, and I’ve seen evidence of this thinking in how they treat their drivers. I’m not sure why this would be extraordinary? On its face those incentives don’t sound bad except that they will incentivize unsafe behavior in edge cases like this.
I think it matters a lot because Amazon doesn’t have their own airline. They contract out their aviation to multiple companies.
The incentive is to pick the lowest bid and that could be a company whose culture creates indirect pressure on pilots to be on time. All it takes is a dispatcher in a small company that is constantly irritated when things are late. Knowing that the other people are going to be angry with you for being late can make you hesitant to go around, causing exactly this type of accident.
Is this what happened? Probably not. Pilots get tunnel vision for any number of reasons.
> Probably just a coincidence that Github started to have issues after beginning their move to Azure at the end of last year.
Right.
I'd like to think that Azure has improved in a meaningful way in the past half a decade or so... but it has not. Maybe less inexplicable 400 errors in random API calls, I guess.
And yet Microsoft keeps posting record growth. Unbelievable.
Not the person you are asking, but definitely yes. Bandwidth isn't the only metric at play here.
Bufferbloat was horrendous with Comcast so latency varied wildly depending on what was happening on the network. The only way around it was to cap download and upload to 80%, and that's a large dent on the already anemic upload. And I had to cap client upload too, otherwise one client could easily saturate upload and now not even TCP ACK packets were being reliably sent.
The main problem isn't cable per se, is the asymmetric link.
EDIT: Also 1Gbps symmetric allows me to backup my NAS offsite without impacting anyone else.
If the culture allows for it, yes.
On final my instructor was talking about the next approach. I heard the words 'go around' and immediately executed one. He realized that (1) that conversation was unnecessary at that phase of the flight and (2) to not use those words unless he wants me to immediately go around :)
After soloing, I sometimes report that I had to go around because I didn't like how the approach or landing was looking like. I got praised for it every time.
So yes, it's all culture.
reply