A note about how aviation looks at mistakes in the US: we have a great program called the ASAP program where if you generally make a mistake (ie not intentionally breaking a rule or being negligent), you can self report to the FAA. They then look at it with representatives of the company and the workers union to determine if it was actually a mistake without a name attached to the report to keep it anonymous. If it was determined to be a mistake and the ASAP is accepted, the FAA cannot take action against the person who made the mistake. The number of people willing to admit to mistakes has increased since implementation and industry wide training has gotten better because of this.
@@mattsadventureswithart5764 we actually use both systems daily. Knots and nautical miles for speed and distance, feet for altitude, miles for reported visibility, and pounds for weights. And while you are trying to talk down on the US for not being metric, European rules mandates imperial measurements also. While kilos are used for weights and meters used for visibility, feet is used for ceilings, knots for speeds, and nautical miles for distances.
What about the math error at the Savannah River nuclear plant that was regularly cracking the pressure vessels. Everyone kept checking the materials used, and engineering practices, but no one verified the actual operating pressures of the vessels, and it turns out that they ran for 40 years at 115% power levels because some engineer had a slide-rule error during its initial construction documentation.
@Fluff-gl6yr Especially as it illustrates how Nuclear power is actually quite a bit safer than anything else. A fossil fuel plant kills thousands of people in its lifetime even working as designed, just cause...cancer and stuff. A nuclear plant running above capacity and constantly having cracks show up in containment vessels and it was just...fine
@@JohnJones1987 PHD students here are paid though. They might need to do some explaining on why they need another year. But they will still get paid for that extra year.
@@timonix2 yeah but your paid barely enough to live, and the work is 16hr a day every day. Its in everyones interest to extend the PhD, as postdocs cost more.
The train thing.. I call that "Fix by post-it" Like when you know that a program crashes if you click a button, but instead of fixing the program, the boss tells you to send an email to everyone, instructing them to put up post-its to their screens saying "don't press that button"
The train thing.. I call that "Fix by post-it" Like when you know that a program crashes if you click a button, but instead of fixing the program, the boss tells you to send an email to everyone, instructing them to put up post-its to their screens saying "don't press that button"
Well it is not really a practical problem, because due to the manual coupling and mixed traffic dominated by passenger trains there are simply no trains that long for various reasons (they are simply not allowed onto the network). Also, those kinds of things are sometimes quite old and very expensive to change as they solution has to be "safety approved" using a very expensive process, it is not at all like just replacing a bug in software. So, if it where a real risk it would not exist. But still, from a modern point of view it is a very strange solution.
True story here: the application my team develops had a bug where, for one client, addresses were being validated on the API service end, and if the address was invalid... it just didn't update. But the API didn't tell the app that it failed; it returned a success code. So the app responded as if the address updated, even though it didn't, and that would break things if it was the first address on file for the customer. I, being a front-end UI developer, reached out to someone on our API services team to explain the problem and ask him to assign a fix for it to one of his developers. His response? "No, we don't need to fix that; just make sure the client doesn't enter invalid addresses, and it'll be fine." That was my first experience with your "fix by Post-It". And I was like... "so we have to tell our clients they can never make any typos or risk corrupting their customers' account data?" Some people. SMH.
@@jeffsergeant Yes those are all horrible ideas. I do not say the solution of that axle counter was good, but lets not forget we do not tak about a normal software solution here, but about an old embedeed system that had to pass rigurious saftey checks, I do not even think it really has software in that sense.
@@IceMetalPunk ideal solution is two-fold; client validation in conjunction with correct success codes from the API response. That way you can have dynamic feedback in the UI preventing them from putting the wrong sorts of things and providing some helpful feedback, but the security of ultimately relying on the same validation server-side. Would be interested to know why you couldn't sync the data back from the server again though to put both client and server back into the same state? That would solve potential issues further down the line, for example server-side data processing and calculated fields. I know this is an entirely uneccessary reply, but I've had a year out of back-end development and that comment just reignited my passion for software development and bug fixing for some strange reason.
5 років тому+590
I'm at peace when Matt's head line up with the monitors edge in the background.
Me too! I was neurotically watching that the whole time and then I read this?!?!! Do you twitch yours legs as the gaps in the dotted lines on the highway pass from view under the hood.of the car?
I do this sort of thing every time I watch a video like this, where a person is meandering in front of some sort of display. There's always some sort of way that I want for them to fit into the image, and my eyes are constantly looking for it while I listen to the talk. I guess it has something to do with our brains liking patterns and things fitting into other things. I think that's part of what makes Tetris such a satisfying game to play.
28:05 bit of a correction: that happened to the USS Yorktown, which at the time was a Ticonderoga class cruiser. The story changes a bit every time I hear it but essentially some sailor was working on the radar, typing in gates so that it doesn’t flag every seagull or cloud as a target. One of the gates didn’t apply in this situation so he put a zero in it. If he had left it blank or written null or anything else, the computer had a check to filter out non number inputs. However, the check read 0 as a valid number to enter into its equations, at which point it divides by zero and the system, running Windows NT, freaks out and shuts down. This computer not only ran the radar, but also propulsion and navigation. The ship ended up dead in the water for about three hours
Imperial units are just bad... They are useless and make math really hard for no rational reason. The SI System makes sense. SI is way superior to imperial. Metric ftw
I can't find anything about elephants and cocaine, just humans ODing on elephant tranquilizer, and poor Tusko who was given a massive 3000x overdose of LSD
Markle2k. Whoa, what a way to go. Super consciously aware every cell in its body is a separate universe, and its body in totality is the multiverse 🤯 ... and Pink Floyd are quite decent actually ...
@@uk1988tb303 Alas, not poor Tusko. Seizures and intense distress marked the last hour and a half of his life. However, about 10 years later, two elephants were given more appropriate doses and seemed to enjoy themselves.
@@Markle2k There are so many things wrong here... 1) The sources I could find say "3000% overdose" (which is very different from "3000x" :) ) 2) while there are some drugs where the dosage is calculated by body surface area, neither cocaine nor LSD is among them - in fact, if you look up the LD50, it is given in mg/kg for both 3) it is still unclear whether it was the LSD that killed Tusko, or the combination of drugs - the test was repeated later (Siegel, 1984) with the exact same dose (.1mg/kg) of LSD alone, and the elephants survived
if it wasn't an American audience, or specifically one American audience familiar with Texas, they'd have missed it also. MP did a Royal Institute talk on UA-cam here: ua-cam.com/video/6JwEYamjXpA/v-deo.html where he used the license plate from Texas. it was a British audience, they all missed the joke too.
In re: spacecraft -- About 35 years ago, while in college, I was working in a cooperative education job for eight months at RCA Astro-Electronics. The department I was working in was updating testing software created for the TIROS-N satellites for the Advanced Tiros N satellite, which had more instruments on it. The point of the testing software was to make sure that the instruments wouldn't shift too much during launch. To do this, they would measure with lasers the precise location of the instruments on the spacecraft put on a shaker table simulating launch, vibrate and then remeasure the positions, and put all the figures into this program to check if it was in specs. Well, on modifying the program (in FORTRAN, btw), I notice that it had a subroutine to calculate the difference between signed numbers. And here's how it did it: First it took the absolute value of the difference of the _absolute value_ of the two inputs, and then if the inputs had different signs, put a minus in front of the result. Essentially Z=ABS(ABS(X)-ABS(Y));If ((X0) ) or ((X>0) and (Y
I have a similar story I worked for rca electronics in the eighties as an onboard sw engineer . During spacecraft operation I analyzed the performance of momentum unloading procedure of one of their telecom satellites erratic behavior was observed and after reviewing the control software I found an error in the digital filter implementation a truncation error in the filter caused instability in performance . Numerical accuracy was improved by implementing 24 bit accuracy and consecutive spacecraft functioned as expected Problem solved! A really interesting assignment at the time
True Swiss would be a different rule for each Kanton
4 роки тому+51
One of the more funny long nerd talks I have seen in full in a long time. What disturbs me is that companies are reluctant to give away how mistakes were made. I think companies easily could obfuscate sensitive portions but still give away generic parts of the error. That would help not only the company itself but human beings as such. But sadly, often cause of errors are not even communicated within the company itself :-(
He sometimes seems to pretend that he is about to start talking about Tau in some of his videos, but then he always goes back to Pi. =P Like for example he can say that he should probably not write one period as "2×Pi" just to make you start thinking "he is gonna mention Tau...!" but then he immediately adds something about including all the integer number of periods other than just 2×Pi. I guess that that's his way to say "fuck Tau, I won't even talk about it even when it might sound like I am about to do that".
30:45 - There's a more acute example than the 'millennium bug': Loudspeaker driver manufacturers would rubber-stamp each of their drivers with the year and month of manufacture. They encoded the year using ONE digit! One couldn't tell if a certain speaker was made in 1955 or 1965!
I absolutely love learning about unforeseen consequences. I'm not sure how varied a maths version of that would seem from the more general "maths mistakes", but it sounds like a book I'd love to read.
"...until you notice that one semicolon." Spot on. Just a couple weeks ago I wrote a script to do something in the cabinet design software I work with, and I couldn't figure out why this one line didn't seem to work. Luckily (?) it is a very forgiving system and let the rest of the script run even with a problem in that line so I didn't notice it for a while. Once I did figure out the line wasn't working I spent hours poking at it: double checking the variables that fed into it, looking for holes in the logic of its formula, rewriting the same formula in different ways, and even trying completely different approaches to accomplish the same thing, but nothing worked. I eventually gave up on it and continued on with the rest of the code. Later on my eyes happened to pass over that line and notice that the comment at the end of the line didn't have the one semicolon in front of it that it was supposed to. Semicolon added, boom it works. In a way it was good that happened, because one of the alternate approaches I developed trying to fix it was a lot more graceful and made it easier to add another feature later. It was still stupidly frustrating, though.
This is a great argument for having fussy systems. The shortcuts and little tricks it doesn't let you get away with, also stops that full day job of finding out the mistake. I have done the same kind of thing countless times when messing around.
When I was in my first year of computer programming in college, my instructor used the Ariane 5 Flight 501 as an example of the importance of writing good code. The way he recounted the story was that the rocket got about 5km in the air and then turned left.
I worked with guys who were nearly on that (actually did Ariane 4, and the post-match Ariane 5 review). It's always the dull stuff that catches you. "For the want of a nail"
The first complete cell above the podium (from our left side view) has a slightly non uniform join with the cell above it toward the left of the common boundary. Sorry to spoil it for you.
@@Flyingdingii Negative. I was a flying crew chief on one of the KC-10s that dragged the F-22s around. I just heard them talking about it during refueling. Some went to Midway and most made it to Hickam. Interestingly, there were Japanese protesters waiting for us to get to arrive in Japan, protesting the arrival of the F-22s. I expect a few of them thought we turned around intentionally. When we finally made it a couple weeks later, there were no protesters to be seen.
55:33 I think "Mentour Pilot" is probably one of the best one's out there and he actually talks about the swiss cheese model. Which I think's funny, but it's actually really informative. 🐘😂🤣🤦🏻♂️ 43:50 It was actually LSD that killed the elephant and it was called Tusko.
@17:45 "Pushing against" a gyroscope will only allow you to change your orientation, it can't change the trajectory. Wikipedia: "Specifically, software that calculated the total impulse produced by thruster firings produced results in pound-force seconds. The trajectory calculation software then used these results-expected to be in newton seconds (incorrect by a factor of 4.45)-to update the predicted position of the spacecraft."
I think the guns being mis-aimed was in the Falklands, and rather than being coriolis-related, it was to do with how that far south, your map projections start to get really warped. If I recall correctly, they worked out firing trajectories on a flat 2D paper map, not taking into account that lines of equal longitude (the vertical lines in a grid map) converge more and more sharply the closer you get to the pole. The artillery projections were calculated on a flat map, the shells landed in the wrong place, and I believe they killed their own troops. (...and everybody died.)
That makes more sense, I was thinking intuitively (and maybe wrongly, I don’t know) the Coriolis Effect is not really even significant enough to make a really fatal error even in the case of something that calls for relatively high precision like nissile/projectile firing trajectory.
@@rickmacdonald5575 Coriolis effect is something you have to take into account, but only if you're doing long-range sniping (where centimeters matter) or very long range artillery (where the ranges are long enough that you can actually miss entirely if you don't).
I'm actually surprised he said the pilots managed to get the F-22s back to base without its systems on. But maybe it was just the navigation system that quit? I've seen footage of an early F-22 testing a touch-and-go maneuvre and the flight systems denying the 'go'-part of that, resulting in a (very expensive) belly flop.
Mr.Parker is a world renowned mathematician, speaker, artist, and philanthropist.. basically he's much smarter than you or I could even imagine so I will take his word for it 🤗
@@zJoriz fly by wire has three or four different modes, depending on the manufacturer. If the full envelope protection quits, it drops down to the more basic modes, still allowing control but with none of the fancy corrections the computer would normally provide. However I could imagine fighter Jets being pretty much unflyable with just „raw input data“ controls, as their CG is very far aft, to create both more manoeuvrability and instability. ie: you pitch up and the plane pitches up uncontrollably.
@@BoleDaPoleyeah - which explains why he doesn't exactly have time to be an aviation electronics buff. The original commenter is correct, Mr. Parker was wrong
It's approximately correct that for the most part, dosage scales across species not with body mass but body surface area (or the 2/3 power of the mass). The truth though is even more complicated, as typical power laws used to fit effective doses for many species have exponents between 0.5 and 1, typically around 0.75. Among humans, the dose for many drugs depends on body fat content, so dosage is often quoted in mg/kg, but that's still not strictly accurate. Linear scaling with mass certainly can't be used to extrapolate doses from a 70 kg human to a 5500 kg elephant.
@@musikSkool I don't think it's similar. Consideration of caliber and gunpowder mass and such for hunting will depend on the ballistic details of the gun and the target. The stopping or killing potential will certainly depend on the animal, but it will depend on things like the density of the skin (zeroth power of mass), distance from skin to vital organs (
@@EebstertheGreat I was thinking that things don't always scale directly. A BB gun will kill a mouse, but scaling that up could lead us to think we need a cannon ball for an elephant. The natives still throw spears, a few dozen or so usually do the trick. Mathematically way more energy than a well placed, legal, piece of metal uses.
@@musikSkool True, bore definitely doesn't scale linearly with the size of the target. Shooting a mouse with a BB gun, most of the energy is lost just getting through the tough skin, which is not as tough as a wildebeest's or whatever, but is not too far off the average for mammals. But if you're hunting an elephant, you don't really want to knock it down dead just like that anyway, because to do that, you really would need a pretty big boom. Not a cannon, granted, but still something bigger than the 2 bore elephant guns people used to break their wrists firing. You want the elephant to bleed to death slowly. You do not, however, want your partridge to bleed slowly as it flies away. I mean, to be clear, I don't want elephants to bleed to death slowly. That's horrible. But I'm assuming a poacher would want that to happen.
@@robertrstevensdid you know that 73 is the 2nd most commonly chosen number when people are asked to pick a random number between 1 and 100? The only number picked more often is 37
Probably a little bit late on this, but the German Solution for 8 Bit Axis Counters is even more hilarious: We limit the Number to 250 so that they never roll over (the counters, not the trains) even if a extra engine is needed because the main one broke down (we've got almost only engines with 4 axis here)
I would like to ask Matt, what I think the final question-asker was actually trying to ask, and that is: "What seems to be the most recurring 'maths in engineering mistake' that humans just can't seem to learn from, and are doomed to repeat?"
In the first _Sonic the Hedgehog_ (Megadrive) it takes eight hits to kill the final boss. You can hit him _nine_ times... but the "boss hit counter" underflows to -255. Good luck getting another 263 hits on him before the (10 min) timer runs out.
I am a retired US Air force Master sergeant, we were stationed at England Air Force Base 1985-89, the moved my family into base housing the first year and we were in a 3bdrm unit multi-family complex. The downstairs was all out of proportion. The plans for the two-story units did not have stairs to get to the upstairs. These were drawn in later and kitchen pass-through goes into the living room
The pictures of cogs is always something to do with the question, "that might work or it might not work.. things have to be done right or it doesnt work " .. its part of the message.
Similar to phantom trains, I had a crashing problem with the "home of the future" on startup that I couldn't repro. On my machine it worked fine, in the test lab there was no problem and when the home was closed and I could test it, it never happened. Then a new guy joined the team and was being shown around the home - it occurred and I started to narrow down the source in the code. When he left, it stopped happening but I knew where it was. I started the system, no problem. I restarted it and ran through the house - it crashed. There was a race condition on the motion detectors! The fix (given that the code was locked down, thereby locking in the bug) - when you start up the system, stand very, very still! Borland C for DOS had an interesting rollover bug in the undo buffer. If you accidentally hit 2 keys at once at exactly the moment when the buffer was supposed to roll over, instead of having a history of 255 characters, it thought you had 254 characters in the keyboard queue and replayed them - including block begin, page down, block end, block delete, save file. That was a frustrating 30 seconds watching it irreversibly destroy my code!
12:25 stars shining through the moon. The earliest example I know is in Coleridge's Rhyme of the Ancient Mariner, where there is a crescent moon with "one bright star within the nether tip"
8:14 I'm gonna have to give this image props for using a proper tooth profile (the involute curve) and not just an arbitrary trapezoid. Someone made sure the gears themselves looked real, if not the gear train as a whole 😅
dont degrade yourself like that. you fill an important spot on YT, and reach a lot of people. love your 4D graphics in your 1st book, would love to see more 4d content
@@mathias3721 Tbqh aussies, and much of the rest of the world have a native understanding for that type of humour. I doubt he evolved it only after having moved
As long as he measures the flour in cubic feet, and milk in troy ounces. Hmm, water could be measured in cubic miles. I just love precision, don't you?
re: stars in the moon, the artist was perhaps referencing Coleridge (you know - for the kids): "'Till clomb above the eastern bar The hornèd Moon, with one bright star Within the nether tip" - The Rhyme of the Ancient Mariner, Samuel Taylor Coleridge
I watch this, genuinley stopped it right now, because a few seconds ago he said, last story, then Q&A. Checked how long I watched it and almost 40mins gone by. Awesome :D
For the Swiss axle counter issue, I wonder if that prohibition came from an actual incident when a train disappeared from the system or if someone foresaw the potential problem when the system was originally specified.
The latter. I work for the DB (German railroad), we have the same regulation, since there are still some old signal boxes on the system working with those old axle counters. Newer systems can count up to 4096, I think. When technological advancements were made in railway technology, trains in Europe became longer. And someone was smart enough to point out that if a train would consist of more than 255 axles, it would reset those old counters. The regulations are still in place, they're right next to me in the shelves I keep my paperwork in :P
“Fly-By-Wire” is *actually* where you don’t control the surfaces directly via hydraulics, but instead use the controls to input desired movement into the computer, that then shifts your control aurfaces while accounting for factors like wind or weight distribution or stuff.
I heard of one about the Navy needing a special nut for one of their ships engines, the engineers order the nut and then we're very anoyed when it was taking so long to come, any way after several months the nut arrives on a flat bed and it absolutely huge, seems the Navy gave the measurements in meters instead or milimeters
Great talk however I would like to take issue with the title ‘maths mistakes’; most of these feel a lot more like software testing mistakes than maths mistakes. I speak as someone who studied maths and later became a test manager for a number of companies. In the past I also worked for the European Space Agency on the Meteosat project and have vivid memories of a live stream of a Meteosat launch when the satellite itself failed and wondering if I would still have a job. On leaving ESA I was also test manager on a project to provide a tracking system for Ariane 5 which would blow the rocket up if it went off course (it was a replacement system for the one that blew up the specific Ariane 5 rocket in your talk). Examples of testing failures I used to quote (although I can’t remember the original source now) were, the Hoover free flight offer where they hadn’t correctly assessed the value of their offer and were inundated with claims, a soft drink promotion with too many winning cans, and a Y2K problem (which actually triggered before 2000) where a stock control system read a date in 2000 as out of date, sent the supposedly out of date stock for destruction and reordered new stock ad infinitum.
I worked in aviation for many years. There was a system where you could report the mistakes you made anonymously. Once a year it was released internally so you could read the reports about things that went wrong and grow your mind about different scenarios you could have never imagined.
Check about a man who made a car plate with "NULL" on it to avoid fines, and then system did send him a huge amount of fines that wasnt detected right on camera an head NULL on the line of numberplate
I edit TV commercials, mostly for car dealerships. One GM requested a commercial with a visual of a balance scale with a $ on one side and a car on the other. Naturally when I animated it I had the car going down and the $ going up to suggest that you get more car for less money. They told me to reverse it, as the visual of the $ going up meant that the price would be increasing. I tried to explain their error but I was overruled.
There is one problem with the story about the swiss axle counters (32mins into the video). While technically true and the regulation obviously existed it had no practical relevance. A train of 256 axles would on average equate a total train length of ~1600m. In Switzerland no train is longer than 750m, there where very few limited experiments with 1500m trains. So in the real world the phantom trains as described in the regulation and portrayed in the video would not exist. Still a nice find by Matt Parker who's videos I love ...
You have to think about this like about the Ariane IV vs. V problem: It's not about the problem being able to occur now, it's about documenting that there might be a problem under certain conditions that might or might not happen in the future just to make sure that when something changes people are at least aware that there is a problem.
While you are technically correct, there are no TRAINS longer than 750m, it is still allowed to have SHUNTING operations with units of wagons longer than that, which is occasionally necessary at freight yards. - A locomotive driver from Germany
I had a maths teacher called Parker before Matt was born. I failed O level maths three times. I later did a far more advanced maths course and exam five years later and scored 98%. I later taught maths.
Correction: You later taught MATH; i.e. MATHEMATICS. So, it's MATH - just as it's ARITHMETIC and not ARITHS. Saying maths or ariths makes you look like a schmuckS. Got it? Alright then! (Just Kiddings!)
I can't give a reference to it, but there was once a motor torpedo boat on exercise, probably 30 years ago, testing a new kind of torpedo. They got the torpedo armed and lined up, and at that moment, the test was called off, and the boat turned around to go home - then blew up. Lives were lost. In the final analysis, the torpedo had a fail-safe mechanism in it, that would cause the torpedo to self-destruct it went off course in the water and turned around to face a friendly boat. It was still armed, and the turn-around sensor had done its job.
Great last question. I wish we'd know if Google's postmortem of mistakes blames the human (as like medicine) or blames the system (as like aviation)? Good point that if blame the people then never learn from the mistake. As the system is the issue.
It's very much the second one. If a human makes a mistake the focus is on why they thought that was the right thing to do and/or why the system didn't prevent them from making the mistake. I wish I could give details, but NDAs etc.
I hope you've already found this out, but "fly-by-wire" is the opposite of what you said. In FbW, pilot initiated actions are sent (by 'electrical' wire) to a computer which then carries out the required actions (via 'electrical' wire) using electro-mechanical actuators.
Similar thing happened to F16s sold to middle eastern allies. The planes were outfitted with different flight control systems, based on region of intended use. Post delivery, customers (nations) could update and modify the systems. Planes ended up being flown from somewhere to Israel. From there, they were unable to take off. Something about the runway being below MSL (sea level) and the code loaded did not have the modification to handle "flying" below MSL. The code attempted to calculate the square root of MSL (ie a negative number) and had a fatal error, and would not allow the planes to take off.
It was the F-15 That flipped at the equator. Luckily the error was found in simulation, because it flipped back "wrong side up" so fast that it would have broken the pilot's neck had it been in a real aircraft.
27:29 Leap years have existed since 45 BC, although not all countries adopted the Gregorian calendar, which amended the rules slightly, at the same time in 1582. Nevertheless, on February 29 2024, many petrol stations in New Zealand failed to operate because the software had not been designed to account for an extra day in February. I think it is safe to assume that the programmers were so young that they had not learned from the Y2K fiasco.
Some drugs are dosed by height, rather than weight. An anesthesiologist explained it to me because cerebrospinal fluid volume is basically dependent on height, while liver size is more related to weight. So depending on the drug and the administration method, you need to dose it differently.
I was confused many years ago when, upon being dismissed by Yes, Tony Kaye and Peter Banks apparently went on to great success with Genesis as Tony Banks. 😜
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
What an honor to be mentioned by you, Matt! Thank you!
Do you know Matt personally?
i was searching for a comment about your channel. glad to see you watched it
Yoooo!!!
big fan
Thank you!
A note about how aviation looks at mistakes in the US: we have a great program called the ASAP program where if you generally make a mistake (ie not intentionally breaking a rule or being negligent), you can self report to the FAA. They then look at it with representatives of the company and the workers union to determine if it was actually a mistake without a name attached to the report to keep it anonymous. If it was determined to be a mistake and the ASAP is accepted, the FAA cannot take action against the person who made the mistake. The number of people willing to admit to mistakes has increased since implementation and industry wide training has gotten better because of this.
Still fail to use metric, though...
@@mattsadventureswithart5764 we actually use both systems daily. Knots and nautical miles for speed and distance, feet for altitude, miles for reported visibility, and pounds for weights. And while you are trying to talk down on the US for not being metric, European rules mandates imperial measurements also. While kilos are used for weights and meters used for visibility, feet is used for ceilings, knots for speeds, and nautical miles for distances.
I love the aviation industry.
we have a similar system in Sweden for people working in healthcare called Lex Maria.
@@bbmikej "we actually use both systems daily"
*proceeds to list only imperial units*
What about the math error at the Savannah River nuclear plant that was regularly cracking the pressure vessels. Everyone kept checking the materials used, and engineering practices, but no one verified the actual operating pressures of the vessels, and it turns out that they ran for 40 years at 115% power levels because some engineer had a slide-rule error during its initial construction documentation.
I don't understand how this was never upvoted. It's a great example.
@@nicholasvinen
Another two years later and still no love for this great comment :(
@Fluff-gl6yr
Especially as it illustrates how Nuclear power is actually quite a bit safer than anything else. A fossil fuel plant kills thousands of people in its lifetime even working as designed, just cause...cancer and stuff. A nuclear plant running above capacity and constantly having cracks show up in containment vessels and it was just...fine
imagine going to your tutor and saying "Sorry my PHD exploded"
9/10 they will tell you it didn't and it's still totally publishable, but you're just gonna need another 1 year of unpaid work.
@@JohnJones1987 PHD students here are paid though. They might need to do some explaining on why they need another year. But they will still get paid for that extra year.
@@timonix2 yeah but your paid barely enough to live, and the work is 16hr a day every day. Its in everyones interest to extend the PhD, as postdocs cost more.
Roger Hallam, a founder of extinction rebellion is doing a Phd in Civil Disobience. Some people should never meet.
The train thing.. I call that "Fix by post-it" Like when you know that a program crashes if you click a button, but instead of fixing the program, the boss tells you to send an email to everyone, instructing them to put up post-its to their screens saying "don't press that button"
The train thing.. I call that "Fix by post-it" Like when you know that a program crashes if you click a button, but instead of fixing the program, the boss tells you to send an email to everyone, instructing them to put up post-its to their screens saying "don't press that button"
Well it is not really a practical problem, because due to the manual coupling and mixed traffic dominated by passenger trains there are simply no trains that long for various reasons (they are simply not allowed onto the network).
Also, those kinds of things are sometimes quite old and very expensive to change as they solution has to be "safety approved" using a very expensive process, it is not at all like just replacing a bug in software.
So, if it where a real risk it would not exist. But still, from a modern point of view it is a very strange solution.
True story here: the application my team develops had a bug where, for one client, addresses were being validated on the API service end, and if the address was invalid... it just didn't update. But the API didn't tell the app that it failed; it returned a success code. So the app responded as if the address updated, even though it didn't, and that would break things if it was the first address on file for the customer. I, being a front-end UI developer, reached out to someone on our API services team to explain the problem and ask him to assign a fix for it to one of his developers. His response? "No, we don't need to fix that; just make sure the client doesn't enter invalid addresses, and it'll be fine."
That was my first experience with your "fix by Post-It". And I was like... "so we have to tell our clients they can never make any typos or risk corrupting their customers' account data?" Some people. SMH.
Or the most annoying user interface feature.. leave the button, but give the user an error message saying not to press the button.
@@jeffsergeant Yes those are all horrible ideas. I do not say the solution of that axle counter was good, but lets not forget we do not tak about a normal software solution here, but about an old embedeed system that had to pass rigurious saftey checks, I do not even think it really has software in that sense.
@@IceMetalPunk ideal solution is two-fold; client validation in conjunction with correct success codes from the API response. That way you can have dynamic feedback in the UI preventing them from putting the wrong sorts of things and providing some helpful feedback, but the security of ultimately relying on the same validation server-side.
Would be interested to know why you couldn't sync the data back from the server again though to put both client and server back into the same state? That would solve potential issues further down the line, for example server-side data processing and calculated fields.
I know this is an entirely uneccessary reply, but I've had a year out of back-end development and that comment just reignited my passion for software development and bug fixing for some strange reason.
I'm at peace when Matt's head line up with the monitors edge in the background.
David Söderström I’m gonna be looking at nothing but that for the rest of the video now
Me too! I was neurotically watching that the whole time and then I read this?!?!! Do you twitch yours legs as the gaps in the dotted lines on the highway pass from view under the hood.of the car?
I do this sort of thing every time I watch a video like this, where a person is meandering in front of some sort of display.
There's always some sort of way that I want for them to fit into the image, and my eyes are constantly looking for it while I listen to the talk.
I guess it has something to do with our brains liking patterns and things fitting into other things.
I think that's part of what makes Tetris such a satisfying game to play.
@@sk8rdman Mattris?
Darn, now I'm super aware of it now! 😂
"It was an orbiter, not a lander"
I think the craft itself disagrees with you there, Matt. It definitely landed, albeit at a high velocity downwards.
Parker lander?
Is that kind of like how a fish on land is breathing for a few minutes?
funny one
Aerobraking supplemented with lithobraking.
It's not a crash, it's a rapid unscheduled disassembly.
28:05 bit of a correction: that happened to the USS Yorktown, which at the time was a Ticonderoga class cruiser. The story changes a bit every time I hear it but essentially some sailor was working on the radar, typing in gates so that it doesn’t flag every seagull or cloud as a target. One of the gates didn’t apply in this situation so he put a zero in it. If he had left it blank or written null or anything else, the computer had a check to filter out non number inputs. However, the check read 0 as a valid number to enter into its equations, at which point it divides by zero and the system, running Windows NT, freaks out and shuts down. This computer not only ran the radar, but also propulsion and navigation. The ship ended up dead in the water for about three hours
@@scottstiener this was the cruiser Yorktown, not the carrier. It served from 1984 to 2004, windows nt came out in 1993
He says the Mars Climate Orbiter was "over 10 years ago".. he wasn't wrong though - it was Sept 1999!
"Pounds... per......... bushel, or something..." xD
Fun fact : you can measure acceleration in pounds per kilogram
@@Anklejbiter F = ma.
So i guess you can also measure it in kilograms(of force) per kilogram. So it's just unitless
Imperial units are just bad... They are useless and make math really hard for no rational reason. The SI System makes sense. SI is way superior to imperial. Metric ftw
Yo stfu British man
@@Anklejbiter Only if you're using "pounds" incorrectly. In lbf/kg, certainly, but just "pounds" are a unit of mass.
I love the long build up to the guy just giggling
“They killed an elephant with cocaine”
I was waiting for something like, ‘well, you can imagine how much cocaine an elephant 🐘 trunk could vacuum up’.
I can't find anything about elephants and cocaine, just humans ODing on elephant tranquilizer, and poor Tusko who was given a massive 3000x overdose of LSD
Markle2k. Whoa, what a way to go. Super consciously aware every cell in its body is a separate universe, and its body in totality is the multiverse 🤯 ... and Pink Floyd are quite decent actually ...
@@uk1988tb303 Alas, not poor Tusko. Seizures and intense distress marked the last hour and a half of his life.
However, about 10 years later, two elephants were given more appropriate doses and seemed to enjoy themselves.
@@Markle2k There are so many things wrong here...
1) The sources I could find say "3000% overdose" (which is very different from "3000x" :) )
2) while there are some drugs where the dosage is calculated by body surface area, neither cocaine nor LSD is among them - in fact, if you look up the LD50, it is given in mg/kg for both
3) it is still unclear whether it was the LSD that killed Tusko, or the combination of drugs - the test was repeated later (Siegel, 1984) with the exact same dose (.1mg/kg) of LSD alone, and the elephants survived
"I'll be around." No, Matt, you'll be a Square.
Not apologising for that.
@Stefan Dingenouts Exactly what I thougt, too :D
And not a perfectly magical one, at that
"the plate's undone by a lone star", completely missed by the audience
if it wasn't an American audience, or specifically one American audience familiar with Texas, they'd have missed it also. MP did a Royal Institute talk on UA-cam here: ua-cam.com/video/6JwEYamjXpA/v-deo.html where he used the license plate from Texas. it was a British audience, they all missed the joke too.
Enlighten us, what's the joke?
@@samwilson5544 The Lone Star State is the official state nickname of Texas.
I CAME DOWN TO COMMENT THIS
How do you know? It's not exactly a laugh out loud joke.
13:46 the lone star joke he threw in there was brilliant.
In re: spacecraft -- About 35 years ago, while in college, I was working in a cooperative education job for eight months at RCA Astro-Electronics. The department I was working in was updating testing software created for the TIROS-N satellites for the Advanced Tiros N satellite, which had more instruments on it. The point of the testing software was to make sure that the instruments wouldn't shift too much during launch. To do this, they would measure with lasers the precise location of the instruments on the spacecraft put on a shaker table simulating launch, vibrate and then remeasure the positions, and put all the figures into this program to check if it was in specs. Well, on modifying the program (in FORTRAN, btw), I notice that it had a subroutine to calculate the difference between signed numbers. And here's how it did it: First it took the absolute value of the difference of the _absolute value_ of the two inputs, and then if the inputs had different signs, put a minus in front of the result. Essentially Z=ABS(ABS(X)-ABS(Y));If ((X0) ) or ((X>0) and (Y
Thanks for sharing your story...
I have a similar story
I worked for rca electronics in the eighties as an onboard sw engineer . During spacecraft operation I analyzed the performance of momentum unloading procedure of one of their telecom satellites erratic behavior was observed and after reviewing the control software I found an error in the digital filter implementation a truncation error in the filter caused instability in performance . Numerical accuracy was improved by implementing 24 bit accuracy and consecutive spacecraft functioned as expected
Problem solved! A really interesting assignment at the time
"That's such a Switzerland solution to the problem"
So true it hurts.
True Swiss would be a different rule for each Kanton
One of the more funny long nerd talks I have seen in full in a long time. What disturbs me is that companies are reluctant to give away how mistakes were made. I think companies easily could obfuscate sensitive portions but still give away generic parts of the error. That would help not only the company itself but human beings as such. But sadly, often cause of errors are not even communicated within the company itself :-(
If Matt does write a sequel to this book, it better be called "Humble Tau", or I'll be triggered.
@BLAIR M Schirmer
Good take but I don't think this is the right comment
That would sound like a Woo-Woo lifestyle book though.
That would go against everything Matt stands for in his mathematical constants.
He sometimes seems to pretend that he is about to start talking about Tau in some of his videos, but then he always goes back to Pi. =P
Like for example he can say that he should probably not write one period as "2×Pi" just to make you start thinking "he is gonna mention Tau...!" but then he immediately adds something about including all the integer number of periods other than just 2×Pi.
I guess that that's his way to say "fuck Tau, I won't even talk about it even when it might sound like I am about to do that".
And at some point in the future, his memoir "Humble i".
30:45 - There's a more acute example than the 'millennium bug':
Loudspeaker driver manufacturers would rubber-stamp each of their drivers with the year and month of manufacture. They encoded the year using ONE digit! One couldn't tell if a certain speaker was made in 1955 or 1965!
I absolutely love learning about unforeseen consequences. I'm not sure how varied a maths version of that would seem from the more general "maths mistakes", but it sounds like a book I'd love to read.
"...until you notice that one semicolon."
Spot on. Just a couple weeks ago I wrote a script to do something in the cabinet design software I work with, and I couldn't figure out why this one line didn't seem to work. Luckily (?) it is a very forgiving system and let the rest of the script run even with a problem in that line so I didn't notice it for a while. Once I did figure out the line wasn't working I spent hours poking at it: double checking the variables that fed into it, looking for holes in the logic of its formula, rewriting the same formula in different ways, and even trying completely different approaches to accomplish the same thing, but nothing worked. I eventually gave up on it and continued on with the rest of the code. Later on my eyes happened to pass over that line and notice that the comment at the end of the line didn't have the one semicolon in front of it that it was supposed to. Semicolon added, boom it works.
In a way it was good that happened, because one of the alternate approaches I developed trying to fix it was a lot more graceful and made it easier to add another feature later. It was still stupidly frustrating, though.
This is a great argument for having fussy systems. The shortcuts and little tricks it doesn't let you get away with, also stops that full day job of finding out the mistake. I have done the same kind of thing countless times when messing around.
Have u tried using lint? Lol
55:20 - "To err is human; to blame it on a computer is even more human." :)
When I was in my first year of computer programming in college, my instructor used the Ariane 5 Flight 501 as an example of the importance of writing good code. The way he recounted the story was that the rocket got about 5km in the air and then turned left.
I worked with guys who were nearly on that (actually did Ariane 4, and the post-match Ariane 5 review). It's always the dull stuff that catches you.
"For the want of a nail"
Matt is awesome. Also, as an AV aficionado, I appreciate the uniformity of the matrix display behind him.
The first complete cell above the podium (from our left side view) has a slightly non uniform join with the cell above it toward the left of the common boundary. Sorry to spoil it for you.
”Funny story about trains, people die aaand... Pacman!”
A bit late to the party, but 27:30 I was on that mission! Two weeks in Hawaii due to the software bug.
So? Did you hear the Windows Start Up sound?
@@Flyingdingii Negative. I was a flying crew chief on one of the KC-10s that dragged the F-22s around. I just heard them talking about it during refueling. Some went to Midway and most made it to Hickam. Interestingly, there were Japanese protesters waiting for us to get to arrive in Japan, protesting the arrival of the F-22s. I expect a few of them thought we turned around intentionally. When we finally made it a couple weeks later, there were no protesters to be seen.
55:33 I think "Mentour Pilot" is probably one of the best one's out there and he actually talks about the swiss cheese model. Which I think's funny, but it's actually really informative.
🐘😂🤣🤦🏻♂️ 43:50 It was actually LSD that killed the elephant and it was called Tusko.
They don't find it easy, they are just people who enjoy how difficult it is. -How did you get so wise Matt
@17:45 "Pushing against" a gyroscope will only allow you to change your orientation, it can't change the trajectory. Wikipedia: "Specifically, software that calculated the total impulse produced by thruster firings produced results in pound-force seconds. The trajectory calculation software then used these results-expected to be in newton seconds (incorrect by a factor of 4.45)-to update the predicted position of the spacecraft."
22:23 "For some of you, this is an excruciating amount of detail. You're like Matt, we know how sensors work"
Me: (whispers) Thank you...
20:10 and now we have another reason to call it the “cluster mission”.
I'm a simple person: I see Matt Parker, I watch the video and click like.
I think the guns being mis-aimed was in the Falklands, and rather than being coriolis-related, it was to do with how that far south, your map projections start to get really warped. If I recall correctly, they worked out firing trajectories on a flat 2D paper map, not taking into account that lines of equal longitude (the vertical lines in a grid map) converge more and more sharply the closer you get to the pole. The artillery projections were calculated on a flat map, the shells landed in the wrong place, and I believe they killed their own troops. (...and everybody died.)
That makes more sense, I was thinking intuitively (and maybe wrongly, I don’t know) the Coriolis Effect is not really even significant enough to make a really fatal error even in the case of something that calls for relatively high precision like nissile/projectile firing trajectory.
@@rickmacdonald5575 Coriolis effect is something you have to take into account, but only if you're doing long-range sniping (where centimeters matter) or very long range artillery (where the ranges are long enough that you can actually miss entirely if you don't).
26:56 Fly-by-wire is the other way round, it’s the type of aircraft that has the controls connected to a computer :)
I'm actually surprised he said the pilots managed to get the F-22s back to base without its systems on. But maybe it was just the navigation system that quit?
I've seen footage of an early F-22 testing a touch-and-go maneuvre and the flight systems denying the 'go'-part of that, resulting in a (very expensive) belly flop.
Mr.Parker is a world renowned mathematician, speaker, artist, and philanthropist.. basically he's much smarter than you or I could even imagine so I will take his word for it 🤗
@@zJoriz fly by wire has three or four different modes, depending on the manufacturer. If the full envelope protection quits, it drops down to the more basic modes, still allowing control but with none of the fancy corrections the computer would normally provide. However I could imagine fighter Jets being pretty much unflyable with just „raw input data“ controls, as their CG is very far aft, to create both more manoeuvrability and instability. ie: you pitch up and the plane pitches up uncontrollably.
@@BoleDaPoleyeah - which explains why he doesn't exactly have time to be an aviation electronics buff. The original commenter is correct, Mr. Parker was wrong
It's approximately correct that for the most part, dosage scales across species not with body mass but body surface area (or the 2/3 power of the mass). The truth though is even more complicated, as typical power laws used to fit effective doses for many species have exponents between 0.5 and 1, typically around 0.75. Among humans, the dose for many drugs depends on body fat content, so dosage is often quoted in mg/kg, but that's still not strictly accurate. Linear scaling with mass certainly can't be used to extrapolate doses from a 70 kg human to a 5500 kg elephant.
Interesting :)
Or bullet diameter or ft. lbs. for hunting. HUGE debate.
@@musikSkool I don't think it's similar. Consideration of caliber and gunpowder mass and such for hunting will depend on the ballistic details of the gun and the target. The stopping or killing potential will certainly depend on the animal, but it will depend on things like the density of the skin (zeroth power of mass), distance from skin to vital organs (
@@EebstertheGreat I was thinking that things don't always scale directly. A BB gun will kill a mouse, but scaling that up could lead us to think we need a cannon ball for an elephant. The natives still throw spears, a few dozen or so usually do the trick. Mathematically way more energy than a well placed, legal, piece of metal uses.
@@musikSkool True, bore definitely doesn't scale linearly with the size of the target. Shooting a mouse with a BB gun, most of the energy is lost just getting through the tough skin, which is not as tough as a wildebeest's or whatever, but is not too far off the average for mammals. But if you're hunting an elephant, you don't really want to knock it down dead just like that anyway, because to do that, you really would need a pretty big boom. Not a cannon, granted, but still something bigger than the 2 bore elephant guns people used to break their wrists firing. You want the elephant to bleed to death slowly. You do not, however, want your partridge to bleed slowly as it flies away.
I mean, to be clear, I don't want elephants to bleed to death slowly. That's horrible. But I'm assuming a poacher would want that to happen.
We choose to do maths....not because they are easy but because they are hard.
Yes every single one of these maths is hard. THIS math is, THAT math is ... yes all of them are - all 73 of them.
@@robertrstevensdid you know that 73 is the 2nd most commonly chosen number when people are asked to pick a random number between 1 and 100? The only number picked more often is 37
13:50 that joke went under the radar xD Nice one!
I came here for this
Probably a little bit late on this, but the German Solution for 8 Bit Axis Counters is even more hilarious: We limit the Number to 250 so that they never roll over (the counters, not the trains) even if a extra engine is needed because the main one broke down (we've got almost only engines with 4 axis here)
Matt: "All that because a couple of lines of code"
Me: intensely stares at a couple of lines of code on my second screen.
I would like to ask Matt, what I think the final question-asker was actually trying to ask, and that is: "What seems to be the most recurring 'maths in engineering mistake' that humans just can't seem to learn from, and are doomed to repeat?"
And after recovering from having his humour thrown in his face he delivered a pretty decent back-peddle answer.
In the first _Sonic the Hedgehog_ (Megadrive) it takes eight hits to kill the final boss. You can hit him _nine_ times... but the "boss hit counter" underflows to -255.
Good luck getting another 263 hits on him before the (10 min) timer runs out.
Omg, the check is equals 0 instead of equal or less than, isn't it?
I am a retired US Air force Master sergeant, we were stationed at England Air Force Base 1985-89, the moved my family into base housing the first year and we were in a 3bdrm unit multi-family complex. The downstairs was all out of proportion. The plans for the two-story units did not have stairs to get to the upstairs. These were drawn in later and kitchen pass-through goes into the living room
"That's how anonymous I can make your stories if you see me after" rofl
The pictures of cogs is always something to do with the question, "that might work or it might not work.. things have to be done right or it doesnt work " .. its part of the message.
I love how these grown men know what a Parker square are and even have the shirt. So funny!!
Similar to phantom trains, I had a crashing problem with the "home of the future" on startup that I couldn't repro. On my machine it worked fine, in the test lab there was no problem and when the home was closed and I could test it, it never happened. Then a new guy joined the team and was being shown around the home - it occurred and I started to narrow down the source in the code. When he left, it stopped happening but I knew where it was. I started the system, no problem. I restarted it and ran through the house - it crashed. There was a race condition on the motion detectors! The fix (given that the code was locked down, thereby locking in the bug) - when you start up the system, stand very, very still!
Borland C for DOS had an interesting rollover bug in the undo buffer. If you accidentally hit 2 keys at once at exactly the moment when the buffer was supposed to roll over, instead of having a history of 255 characters, it thought you had 254 characters in the keyboard queue and replayed them - including block begin, page down, block end, block delete, save file. That was a frustrating 30 seconds watching it irreversibly destroy my code!
"if you support me on Patreon that's how I waste your money"
I died
12:25 stars shining through the moon. The earliest example I know is in Coleridge's Rhyme of the Ancient Mariner, where there is a crescent moon with "one bright star within the nether tip"
I can't believe this guy never mentioned any of my Math exams.
8:14 I'm gonna have to give this image props for using a proper tooth profile (the involute curve) and not just an arbitrary trapezoid. Someone made sure the gears themselves looked real, if not the gear train as a whole 😅
dont degrade yourself like that. you fill an important spot on YT, and reach a lot of people.
love your 4D graphics in your 1st book, would love to see more 4d content
nomen nominandum It's not degrading. It's British. 😉
Self deprecating humour is quite a British thing. Nothing wrong with that. In fact, I find it quite sympathetic.
He’s Australian
@@joedrave945 But he lives and works in Britain and has done so for years
@@mathias3721 Tbqh aussies, and much of the rest of the world have a native understanding for that type of humour. I doubt he evolved it only after having moved
5:20 - So when are you going to release your cook book ? ;-)
yeah, I want to properly cook celebrities, too...
scnr
As long as he measures the flour in cubic feet, and milk in troy ounces. Hmm, water could be measured in cubic miles. I just love precision, don't you?
in that case use "Bizarre Units used by Scientists - Sixty Symbols" "watch?v=hsEB65Q4kHI" they already started
Should he do such a book it simply must be called "Humble Pie".
re: stars in the moon, the artist was perhaps referencing Coleridge (you know - for the kids):
"'Till clomb above the eastern bar
The hornèd Moon, with one bright star
Within the nether tip"
- The Rhyme of the Ancient Mariner, Samuel Taylor Coleridge
I watch this, genuinley stopped it right now, because a few seconds ago he said, last story, then Q&A. Checked how long I watched it and almost 40mins gone by.
Awesome :D
For the Swiss axle counter issue, I wonder if that prohibition came from an actual incident when a train disappeared from the system or if someone foresaw the potential problem when the system was originally specified.
The latter. I work for the DB (German railroad), we have the same regulation, since there are still some old signal boxes on the system working with those old axle counters. Newer systems can count up to 4096, I think. When technological advancements were made in railway technology, trains in Europe became longer. And someone was smart enough to point out that if a train would consist of more than 255 axles, it would reset those old counters. The regulations are still in place, they're right next to me in the shelves I keep my paperwork in :P
“Fly-By-Wire” is *actually* where you don’t control the surfaces directly via hydraulics, but instead use the controls to input desired movement into the computer, that then shifts your control aurfaces while accounting for factors like wind or weight distribution or stuff.
I heard of one about the Navy needing a special nut for one of their ships engines, the engineers order the nut and then we're very anoyed when it was taking so long to come, any way after several months the nut arrives on a flat bed and it absolutely huge, seems the Navy gave the measurements in meters instead or milimeters
Great talk however I would like to take issue with the title ‘maths mistakes’; most of these feel a lot more like software testing mistakes than maths mistakes. I speak as someone who studied maths and later became a test manager for a number of companies. In the past I also worked for the European Space Agency on the Meteosat project and have vivid memories of a live stream of a Meteosat launch when the satellite itself failed and wondering if I would still have a job. On leaving ESA I was also test manager on a project to provide a tracking system for Ariane 5 which would blow the rocket up if it went off course (it was a replacement system for the one that blew up the specific Ariane 5 rocket in your talk). Examples of testing failures I used to quote (although I can’t remember the original source now) were, the Hoover free flight offer where they hadn’t correctly assessed the value of their offer and were inundated with claims, a soft drink promotion with too many winning cans, and a Y2K problem (which actually triggered before 2000) where a stock control system read a date in 2000 as out of date, sent the supposedly out of date stock for destruction and reordered new stock ad infinitum.
I'm a simple person: I see Matt Parker, I watch the video and click like.
Will the sequel be called Humble Tau?
That would have to be Steve Moulds book
Matt: More detail than normal.
Me: I already heard this story.
Boeing Max needs to be in the next edition of the book.....
Well done raising it in the talk
What an entertaining and educational talk! Thanks for talk and I hope to read the book some day.
I worked in aviation for many years. There was a system where you could report the mistakes you made anonymously. Once a year it was released internally so you could read the reports about things that went wrong and grow your mind about different scenarios you could have never imagined.
Check about a man who made a car plate with "NULL" on it to avoid fines, and then system did send him a huge amount of fines that wasnt detected right on camera an head NULL on the line of numberplate
lol! Maybe he can wiggle his way out of all of them, even the correct ones?
*and had
Great to hear that Brody gets a mention!
No mentioning Brady though
Bradley
@@andymcl92 Shame that Dirk at Veristablium didn't get a mention, though.
12:41 there is also a star right next to Ernie's pyjamas, in front of a hill, dangerously close to Earth. Nobody noticed?
@57:21 The sunlight and shadow on that building in the upper right of the screen behind Matt looks like an Amiga mouse pointer.
I don't feel like the audience are appreciating this guy enough!!
I edit TV commercials, mostly for car dealerships. One GM requested a commercial with a visual of a balance scale with a $ on one side and a car on the other. Naturally when I animated it I had the car going down and the $ going up to suggest that you get more car for less money. They told me to reverse it, as the visual of the $ going up meant that the price would be increasing. I tried to explain their error but I was overruled.
There is one problem with the story about the swiss axle counters (32mins into the video). While technically true and the regulation obviously existed it had no practical relevance. A train of 256 axles would on average equate a total train length of ~1600m. In Switzerland no train is longer than 750m, there where very few limited experiments with 1500m trains. So in the real world the phantom trains as described in the regulation and portrayed in the video would not exist. Still a nice find by Matt Parker who's videos I love ...
If someone wanted they could make trains with half the axle distance and make it fuck up, but that would be illegal.
You have to think about this like about the Ariane IV vs. V problem: It's not about the problem being able to occur now, it's about documenting that there might be a problem under certain conditions that might or might not happen in the future just to make sure that when something changes people are at least aware that there is a problem.
While you are technically correct, there are no TRAINS longer than 750m, it is still allowed to have SHUNTING operations with units of wagons longer than that, which is occasionally necessary at freight yards. - A locomotive driver from Germany
LOL..... I saw that poster at 7:15 and thought the same thing.......this is an educational poster and the gears are jammed LOL
I had a maths teacher called Parker before Matt was born. I failed O level maths three times. I later did a far more advanced maths course and exam five years later and scored 98%. I later taught maths.
Correction: You later taught MATH; i.e. MATHEMATICS. So, it's MATH - just as it's ARITHMETIC and not ARITHS.
Saying maths or ariths makes you look like a schmuckS. Got it? Alright then! (Just Kiddings!)
@@robertrstevens What are you gonna do about it, throw tea in the ocean?
I can't give a reference to it, but there was once a motor torpedo boat on exercise, probably 30 years ago, testing a new kind of torpedo. They got the torpedo armed and lined up, and at that moment, the test was called off, and the boat turned around to go home - then blew up. Lives were lost. In the final analysis, the torpedo had a fail-safe mechanism in it, that would cause the torpedo to self-destruct it went off course in the water and turned around to face a friendly boat. It was still armed, and the turn-around sensor had done its job.
41:27 Where the join is in the rows of screens, the hyphen in the URL is hidden.
Great last question. I wish we'd know if Google's postmortem of mistakes blames the human (as like medicine) or blames the system (as like aviation)?
Good point that if blame the people then never learn from the mistake. As the system is the issue.
It's very much the second one. If a human makes a mistake the focus is on why they thought that was the right thing to do and/or why the system didn't prevent them from making the mistake. I wish I could give details, but NDAs etc.
Blameless postmortems are essentially industry standard at this point too
43:55 those two in the background move in perfect sync for a bit lol
I hope you've already found this out, but "fly-by-wire" is the opposite of what you said. In FbW, pilot initiated actions are sent (by 'electrical' wire) to a computer which then carries out the required actions (via 'electrical' wire) using electro-mechanical actuators.
"Aviation is phenomenal in terms of how they deal with mistakes"
Boeing: HA!
But everyone knows Duna's atmosphere starts at 45km! MCO should have been fine!
They had the realism overhaul mod installed
Similar thing happened to F16s sold to middle eastern allies. The planes were outfitted with different flight control systems, based on region of intended use. Post delivery, customers (nations) could update and modify the systems. Planes ended up being flown from somewhere to Israel. From there, they were unable to take off. Something about the runway being below MSL (sea level) and the code loaded did not have the modification to handle "flying" below MSL. The code attempted to calculate the square root of MSL (ie a negative number) and had a fatal error, and would not allow the planes to take off.
"You can tolerate a lot for a single year"...
2020: Uh oh...
43:43 love the first 'question'.
Ex Teachers can become some of the best educational UA-camrs, so good at speaking and explaining
Step Daughter is keen on maths, unlike me - have just bought your book. Good job!
@13:45 that's why it's the "lone star" state
It was the F-15 That flipped at the equator. Luckily the error was found in simulation, because it flipped back "wrong side up" so fast that it would have broken the pilot's neck had it been in a real aircraft.
40:16 - Yes, but did you use the same *water*? :)
Matt, fly-by-wire means that the controls are electrically connected instead of physically by cables and rods.
This was a great talk. Fascinating to listen to.
at 43:51 the two people on either side of elephant cocaine guy laugh and move forward in the exact same way
Something in the matrix has changed
I’m whelmed
27:29 Leap years have existed since 45 BC, although not all countries adopted the Gregorian calendar, which amended the rules slightly, at the same time in 1582. Nevertheless, on February 29 2024, many petrol stations in New Zealand failed to operate because the software had not been designed to account for an extra day in February. I think it is safe to assume that the programmers were so young that they had not learned from the Y2K fiasco.
21:09 - UCL, not UCLA as the subtitles state (it's clear from the subsequent description but still, he was also clear when he said UCL)
First advertising audible and then complaining about Adsense not giving enough money. Absolute mad lad.
The maths can save your life by helping you avoid geometric anomalies: vicious circles, love triangles and square heads.
Some drugs are dosed by height, rather than weight. An anesthesiologist explained it to me because cerebrospinal fluid volume is basically dependent on height, while liver size is more related to weight. So depending on the drug and the administration method, you need to dose it differently.
This is neither Trey Parker nor Matt Stone.
Agreed. I was disappointed, but I like this video still at least
I was confused many years ago when, upon being dismissed by Yes, Tony Kaye and Peter Banks apparently went on to great success with Genesis as Tony Banks. 😜
@@jeremyhelm2833 what
@@JoshBurcham104 ha ha... It was merely a comment on how we can combine/conflate/confuse "paired names".
@@jeremyhelm2833 ohhh sorry I read that completely wrong and with the assumption it was meant to be about this video
Perth? Oh! I loved you before I knew you were Australian, but now I'm sold for life. Love from Melbourne.
Wild guess: The trivial error leading to an aesthetic difference = Facial animations in Mass Effect Andromeda
you took an apple to the google talk? That's balls Matt!
Matt: I didn't think this was gonna be--
That one dude: AHAHAHAHAHAHAHA
Me: Oohhhhh boy
The two pound coin mistake is hugely significant.
Imagine archeologists 3000 years in the future and their debilitating debate on this.😮 😮