It is interesting to see this bifurcation in action.
Hey software engineers - you know that working weekends is unusual, right? Like... please tell me someone has at least negotiated your right to only work 5 days a week so if you're working a weekend you get Monday and Tuesday off.
If not... Has anyone told y'all you should unionize?
What seems to be unique in American companies is you’re expected to work shifts or nights but also work m-f 9-5 at the same time, which is really weird.
Same with of call, if you get called at 3am on an on/call rota for a specialised third line escalation many companies still expect you to work the next day, and they might not even pay you for being on call?!
I mean, you make it sound like releases fail often. For our team I think we have only seen one failure in the last two years needing a fix after hours (going into the weekend)?
The other option is to fail during the workweek. If the software is directly generating money for the users and the developers are judged on what actual business value they provide then failure during business hours is worse.
Yes. That's why people work staggered schedules. Folks who work weekends at shops usually (and should) have two other days off in the week.
People literally fought, bled, and died for our right to not do capitalism 24/7/365, because with no back-pressure that's what the efficiency engine will demand of us.
And part of that is software engineers doing deployments after-hours for their customers. If your company or country is any good, they'll give you double time off during normal hours.
For industries that serve customer bases that are down-cycled on weekends, the dominant effect is "Deploy on Friday to minimize customer disruption chance."
For industries that operate with a 24/7 uptime expectation, the dominant effect is "do not deploy on Friday so you don't have to pay for your expensive software engineers pulling extra hours on a weekend. Much better to have disruption while the folks most qualified to fix it are in-house and alert."
The curse actually exists in every codebase; LISP just makes it more obvious.
I previously administered a service in Python that included
- a postgres backend
- alembic to handle migrations and sqlalchemy to do ORM bindings
- strawberry to supply a GraphQL API
- an autogen library to create a Python wrapper for that API, and then additional hand-written glue atop that because the autogen had flaws.
There is some chance that if you get air-dropped into our codebase, you might be familiar with all those pieces. But if not, you still have a learning curve to get what's going on.
The only advantage Java, Python, etc. ecosystems have is popularity, which makes it more likely that someone's bespoke solution has become standard enough that you might have heard of it before. There are still probably 2 or 3 dominant frameworks that you might or might not have seen entering a new codebase (and then a bunch of special-casing and glue code to match the almost-there abstractions to the actual problem domain).
Nerve impulses travel at about 120 m/s, max, and that's along long myelated runs. Cohering raw pain signal into the experience of pain takes at least 150 msec according to the best measurements we have on the topic.
The vertical speed of the plane alone at last reported speed indication exceeds the speed of neuron transmission along myelated nerve tissue. This impact event is mechanically impossible to feel.
High-speed camera footage of rocket sleds and fuselage testing is fascinating stuff.
You can see the macroscopic deformation fail to transit the body of the impacting object with enough speed to make gross deformation happen as it collides. The front of the rocket body is literally turning to a vapor at the impact site, and the tail assembly is 100% fine.
And if they were so iced over that control surfaces weren't responding and the wings were no longer generating lift, at that point they were well past the "Anything we do is going to have any effect whatsoever on the future" point.
I don't intend to listen to the audio. Second-hand, it sounds as though they did absolutely everything they could after hitting the cell, and the only way to have avoided this whole situation was "Don't fly that route that day."
... a problem that, in general, we see more often in private-jet and single-engine aviation than commercial-carrier aviation. Far more incentives to make a really, really bad call... And when the bad call happens, the Venn diagram of victims and responsible parties tends to have a lot more overlap, so there's, practically speaking, fewer consequences to discourage such bad decisionmaking in the future (can't meaningfully punish the dead, and the dead can't learn from experience what a bad call "smells" like on the lead-up to it).
I don't agree they had no way to avoid this. Every accident is a chain of mistakes, gaps or mechanical issues. We don't know the whole story here, but I do know that planes of this class are not given up for dead when they hit a surprise weather system. If they are, that means they missed something earlier - weather radar was misinterpreted or a bad judgment call was made.
Forward velocity is proportional to lift, assuming your lifting surfaces still work. If you're stalling, standard practice is to apply power and get the nose down so that gravity and engine thrust are working in your favor to put air back under your wings.
In this case though, it sounds like the icing was much worse than they thought and fatally compromised the aerodynamics of the wings, and then the overspeed would have torn at the wings and fuselage... In that circumstance, you're no longer flying a plane, you're riding a javelin.
Training would generally still encourage the pilots to apply power; in the worst-case scenario (here), failing to apply power would not have made the crash survivably slower, so the sum total of best bad actions is still "Apply power and hope you're not in the worst-case scenario."
A fully-fueled private jet is an inefficient missile, but it exceeds the raw chemical energy of most in-theater single-target tactical missiles (although the energy conversion is far less precise and efficient).
But yes, that's a lot of kinetic mass dead-stopping on a hard surface and 1 to 2 kiloliters of jet fuel.
I think, with this many decades of hindsight, it is not unfair to claim The Inner Light is TNG's City on the Edge of Forever.
It's every performer in the episode hitting on all cylinders on a script that is doing what science fiction is for.
ETA: Having poked at it a bit, I have just learned that Morgan Gendel and Peter Allen Fields shared a Hugo Award for Best Dramatic Presentation for that script... The first time a Star Trek script won a Hugo since the previous award to Harlan Ellison for the script for City on the Edge of Forever. Nice to know there's a semi-objective metric by which the episodes are already rated as equivalently impactful.
Hey software engineers - you know that working weekends is unusual, right? Like... please tell me someone has at least negotiated your right to only work 5 days a week so if you're working a weekend you get Monday and Tuesday off.
If not... Has anyone told y'all you should unionize?
reply