178 karma · joined February 16, 2023
For the 16mm movie cameras in this case, they probably selected frames from rigidly mounted cameras with little subject motion to get a good result out of it. Glenn strapped in tight in his tiny cockpit probably provided them with a decent number of frames they could stack without introducing much motion blur. In fact, you can see a bit of blurring at the end of one of the white straps center frame in that shot: https://cdn.arstechnica.net/wp-content/uploads/2025/09/03b-G...
It's a pretty common technique in astrophotography. Here's a page that goes into some more detail in that context: https://clarkvision.com/articles/image-stacking-methods/
Another historical example I find myself thinking about is the huge number of objects that moved into a disposable category in the last century or so. What used to be built entirely by skilled hands is now the prerogative of the machine and thus a certain base level of maintainability is no longer guaranteed in even the worst-designed widget.
Yes, AI will mean more software is "written" than before, but more will be thrown away too. The allure of the re-write is nothing new, but now we'll do it not because we think we can do it better the second time, but because the original is too broken to keep using and starting over is just so much cheaper.
Soon at CRUD App HQ (if not already): "Last year's pg_dump is this year's prompt."
If you're just putting in a destination and getting a fastest route (much like you'd do in Google Maps), then I didn't see much benefit to the premium version.
According to what I recall of Allan McDonald's version of things, they had a good amount of data that colder temperatures meant worse sealing performance from the o-rings (soot making its way past the first o-ring and in some cases damaging the second, basically). Like you said, it was a well-known issue in some circles. They also knew the Challenger launch the next morning would be very cold indeed, something wild like at or just above freezing, I think.
The engineers at Thiokol raised their concerns and were asked what a safe temperature to launch is and said something like 53F, basing this on the fact that a previous launch at that temp was successful. NASA (and Thiokol) management balked at this because the booster's certified minimum launch temp was something lower like 30 or 40F. Then they basically asked them to prove it would catastrophically fail at the temperatures expected the next morning, which they couldn't conclusively do since they didn't have the data to back it up. Management reversed the no-go recommendation based on this.
So yes, the o-rings performed as expected insofar as colder = worse, but it was a matter of how much worse at temperatures lower than any successful previous launch.
Some things do run very quickly, for sure, but so many of the high touch pieces of code out there from big name corps have some of the worst performance. Hundreds of millions of people use Teams, and many of them use it a lot throughout the day. You must just be getting lucky in what apps you use on a regular basis.
https://twitter.com/RazorwireRyan/status/1735753526167347232
Ed Pierson, a Boeing whistleblower on quality, has also commented on similar efforts by the company a couple of months later. https://www.edpierson.com/removal-of-quality-control-inspect...
In this case no, because the way the MCAS system operated was to actuate the stabilizer trim which changes the angle of the entire huge tail plane (the horizontal part of the tail). For the most part the yoke controls the elevator (a smaller flap on the trailing edge of the tail plane), so the pitch control authority available in the yoke movement is not enough to override the adjustment to the tail plane trim MCAS was making.
Once MCAS moved the trim far enough, you couldn't raise the nose with the yoke alone. To correct it, pilots needed to deactivate the trim adjustment motor ("stab trim cut-out" you might have heard about) and manually re-trim the tail plane by folding out a literal crank and spinning a wheel by their legs in the cockpit[1]. The concept of doing this was not new with the MAX (similar procedures around trim system malfunctions existed), but what was new was that MCAS existed in the first place, that it could repeatedly activate if the erroneous inputs were still present, and that it could move the trim quite far before pilots realized what was happening. As I understand it that is pretty different than a traditional runaway trim malfunction for which they'd had training for. I believe that looks more like a stuck switch making a constant movement of the trim until you hit the cut-out. If you cut it back in, either it immediately starts moving again and you know you have a problem or it doesn't and leaves you wondering.
[1](https://www.trbimg.com/img-5d0ba28b/turbine/ct-biz-wp-boeing...)
Oh and, it actually does do OpenAPI specs for REST and even mock services and all that, so I'm delighted to share that it's actually relevant to this post! :^) What are you waiting for?
Probably true since it doesn't appear like they're a game engine company any more. The enshittification machine is rumbling to life.
https://www.reuters.com/technology/reddit-aims-ipo-second-ha...