8 ms·
This is a pretty low quality, low effort rant of the "back in my day" variety. "Engineers nowadays don't know what they are doing simply because I say so" I ha
by mrguyorama 4y ago
This is a pretty low quality, low effort rant of the "back in my day" variety. "Engineers nowadays don't know what they are doing simply because I say so"
I have many engineer friends. They have no problem understanding the math and physics and concepts of things like statics analysis and don't use simulation "because they don't understand the problem" but because simulations allow you to use more complicated, or more unusual structures that classical methods simply cannot work with.
Your stupid slide rule and winging cannot compete with the power that you get from actually using the math that your older methods just approximate. Turns out, much more accurate simulation allows for BETTER SOLUTIONS.
Stop being a crotchety and elitist angry person and try to understand the way things are going, instead of casting new methods aside because you don't personally understand or get them.
- kabdib 4y agoI used slide rules a bunch when I was in high school, just before calculators killed them forever. I felt that I had a better grasp of what a particular computation meant. The need to keep track of orders of magnitude and so on helped me catch errors that would have slipped through if I was just pressing buttons and copying down results. The practice helped me later on with "back of the envelope" calculations. It doesn't make me nostalgic for slide rules, though. Give me an HP calculator any day.
- bombcar 4y agoThat’s the exact point - you worked through it and got a “feel” for how the variables worked, so even if you use a calculator you get a feel if things are off. Same thing happens everywhere - people don’t understand enough to do something like ballparking some numbers to check if they’re at all reasonable - but this is useful.
- possiblydrunk 4y ago> Stop being a crotchety and elitist angry person ... Sounds familiar, like I just read an example of it :/
- GeorgeTirebiter 4y agotakes one to know one (yikes). I do find it tough when readers attempt to deign a writer's mental state from some groups of characters strung together. Why, some might call that mindreading. '-)
- possiblydrunk 4y agoAnger isn't needed to make a good point! Politeness works just as well :)
- GeorgeTirebiter 4y agoI'm sorry, I'm not making myself clear. The Author generates strings of characters (that ultimately form 'words' and 'sentences' and 'paragraphs' in aggregate). These character strings are chosen by an author to suggest a 'frame of mind' in order to best get her point across. So when an author of fiction causes a character to say things that are interpreted as angry, it doesn't mean the author herself is, in fact, angry. Therefore, unless we know something not in evidence besides the author's strings of characters, drawing conclusions as to the writer's mental state is ... odd. Even for pieces of non-fiction.
- possiblydrunk 4y agoNot directed at your comment. But is calling a person a "crotchety and elitist angry person" necessary to the point being made? Seems a bit ad hominem to me.
- lantry 4y ago> when readers attempt to deign a writer's mental state from some groups of characters strung together this is how written communication works
- Dylan16807 4y agoSomewhat crotchety, but I don't think they come across as elitist.
- dwater 4y agoI had a stats professor theorize that at some point all stats calculations would be done with simulations instead of formulas, since formulas are simplified models of reality whereas simulations can capture much more of the complexity if properly constructed. This was 10 or 15 years ago and the feeling was computers were either fast enough already or would be soon enough for most problems. This came up as a result of a similar observation about the transition from tables to graphing calculators for probability distributions and things like that.
- stdbrouw 4y agoPlenty of computing power 15 years ago for bootstrapping (simulation-based estimation of uncertainty for an analytically estimated model), today plenty for the entire model itself (Bayesian MCMC, frequentist optimization-based methods)
- CrazyStat 4y agoIf you read the original 1979 bootstrap paper, one of the delightful things about it is that it discusses the computational cost (literally, in dollars) to rent time for the procedure on a shared mainframe.
- blt 4y agoIt's true. Basically every estimation or inference problem can be solved by MCMC. The only reason not to do so is a lack of computational power.
- operator-name 4y agoThe majority of estimation problems have either: - too much uncertainty - extremely relaxed tolerances for acceptable answers and are performed in people's heads or simple napkin/grade school maths. It's not about computational power, it's about what's right for the job.
- WalterBright 4y agoI recall a study where the researchers doctored calculators to give the wrong answer, and gave them to high school students for their work. The calculators had to produce an answer that was off by more than a factor of 2 before the students suspected something might be wrong. Back in the 80s at Boeing, the experienced engineers were deeply suspicious of any "computer numbers" because they'd been burned too many times by garbage results pushed by the computer department. I was the only person in my group (of about 30) to use a computer to calculate things. The others used calculators and graphical methods. My lead engineer didn't want any "computer numbers". I persisted, so he set up a competition between me and his best graphical method draftsman. One of the numbers I generated didn't match the graphical results. My lead said "see, you can't trust those computer numbers!" The graphics guy said he'd recheck that one. A couple hours later, he said he'd made a mistake and the computer numbers were correct. (Note the "couple hours" to get one number.) After that, my lead only trusted computer numbers from me, and directed a lot of the calculation work to me. (All designs were double checked by a separate group, and then validated on the test stand. Correcting a mistake by then, however, got very expensive.)
- SaberTail 4y agoI'm skeptical that students given a doctored slide rule would fare any better in a similar study. There's nothing inherent to a slide rule that gives you a better sense for what the result should be. You do have to keep track of order of magnitude, but that's only going to marginally help you if we're talking about factor of 2 errors.
- WalterBright 4y agoA slide rule has the advantage in that you can see it working and how it works. A calculator has no such feedback.
- Ancapistani 4y ago> A calculator has no such feedback. That's an interesting thought. There's no reason a calculator has to output only a number - with the computing power and displays at our disposal today, we could easily draw and/or animate a virtual slide rule. A virtual slide rule probably wouldn't be the best option, though. It's just a visual metaphor for how the values in the calculation relate to one another, and it's one that's only going to be useful for someone who has learned to use a slide rule. I wonder if there might be an effective, generic way to present calculations visually in a way that requires little or no training to understand. Has anyone done this?
- operator-name 4y agoI find your comment surprising as I didn't get this impression. I think the author has a valid point against deterministic thinking, something that has increased as computers and numerical calculations have become cheaper. > Performing calculations with slide rules was part of what forced generations of scientists and engineers to _understand the approximations they were using to solve problems_. I think this is a valid and pretty strong point. Just as in science significant figures matter, the same does for all thinking. In the given example, it is undeniable that calculators don't propogate uncertainty the same way that a physical slide rule does. > He did not want to be bothered with the actual truth (i.e. flaws and inaccuracies in the simulation), because he was simply not interested. Models by definition do not capture all the intricacies, and it's important to have an instinct about what matters and an instruct about the expected model result. It is commonplace for simple models to ignore uncertainty and tolerances as a factor (for simulation speed or complexity reason), which can lead to drastic differences in simulated and true outcomes. Any reasonably complex model is also likely to be chaotic, but it can be difficult to appreciate when the model is useful, and when it isn't. I think it's quite easy to forget these nuances, especially if you don't fully appreciate the field you're modeling. > Am I arguing that we should throw away our computers and go back to slide rules? Absolutely not! Some problems can only be solved by computer simulation--because we really do not know enough to solve them any other way. > But, most design problems can be solved with simpler, less expensive, less time-consuming methods and tools and more experience and knowledge of basic principles. > wasting time with tools that are not appropriate for their jobs In my mind, this is much aligned with "premature optimisation is the root of all evil", and its something I've become extremely aware of as I've started getting into hobby CNC. Through this process I've had to learn when precision matter and when it can just be eyeballed, what can be approximated and how much of a fudge factor to use. Floating point accurate simulations just need to be good enough, and it's always expected that issues will arise in the real world. Most processes are forgiving enough that issues can be worked around, and it's a complete waste of time to try to anticipate everything. At least in my scope of vision, simulations and modeling with uncertainty or tolerances is rare. Models that acknowledge their internal chaotic nature are more common, but not common enough. Modeling with uncertainty is inherently complex, and I'd hazard a guess that your engineering friends are careful enough to only use simulations in specific and key areas that it has an advantage, but are likewise happy to use approximations where necessary.
- api 4y agoAlso on the fighter aircraft thing: I'm not sure simulation is why present designs take so long. It's more likely a mixture of bureaucracy, cost-plus contracting creating perverse incentives to stretch out development, and insisting on pushing the envelope as far as possible and maybe past a point of diminishing returns. The latter might indeed involve a lot of gratuitous simulation and hard number crunching, but it's to get to places you just couldn't get with classical approaches. Of course you can debate the diminishing returns angle and whether that extra 5-10% performance is worth the effort.
- zppln 4y agoAnother crucial point is that a fighter fielded today is expected to have feature parity with the previous one that was continuously upgraded for the past 30 years.
- bitL 4y agoYou see it all the time, "Deep Learning is not needed, in reality all you need is linear/logistic regression!" etc. Then you have to work with such people that sabotage anything outside their narrow view of how things have to be.
- Ancapistani 4y agoAh, but they hold those views for a reason! It's likely that they've seen deep learning used to solve problems in the past that are more suitable to a simple regression. They may not have seen it used to solve problems where regressions failed. In your place, I'd dive into why they feel the way they do. Maybe they're right! More likely, maybe you're using deep learning for jobs it isn't best suited.
- bitL 4y agoThis attitude typically isn't about the "best tool for the job", i.e. do I really need DL or are decision trees or some regression sufficient for what I need to achieve? But about the persistent "you don't need DL at all!" stance. In a way I understand it, for example if somebody finished their computer vision PhD before Deep Learning and don't want to admit their knowledge is now next to useless for most industry cases...
- ska 4y ago> and don't want to admit their knowledge is now next to useless for most industry cases... Jokes on both of them: the DL knowledge is also next to useless for most industry cases.
- aaroninsf 4y agoRead this comment, then read the post, and thought, well, I appreciate the author's thrust, which I would interpret as "become fluent in the fundamentals first" salted and undermined by yes a crotchety get off my lawn overstatement of the utility and value of doing so. Agree with the sentiment, I think, though. Personal comment: I think you (mrguyorama) are correct in pointing to the complexity of contemporary structures/problems. I would state this in terms of the where contemporary progress is being, what sorts of problems are being worked on, etc: considerably further into the fractal of hard problems, and in new regions of the problem domain which were not assailable through manual computation. The tools being used in other words are necessary and appropriate for what kinds of work are being done today. Aircraft design (etc.) today is only superficially related to what it was in the author's day. We are now in the hard 20% in a lot of ways.
- johnfn 4y agoHaha, yeah. This rant reminded me of people who don’t need any new fangled languages/frameworks - they’re perfectly ok getting by in C/ASM. Neglecting that the entire point of abstraction is to achieve more complex tasks by hiding the details.
- hangonhn 4y agoAgreed. I can't help but think the approach he advocates is actually very limiting. When your instruments are more crude, you have to be more conservative in your approach. The accuracy of modern approaches allow us to be more open minded and creative in our solutions. When the cost of trying new materials and designs is just a simulation, you can afford to try really interesting new designs. That's a capability you can't realistically have with a slide rule.
- dieselgate 4y agoI don’t know, I agree with some of what you’re saying but don’t understand why you use such a negative tone. Slide rules are awesome but I’d never say we should all use them now. Everything was built on the shoulders of giants
- tqi 4y ago"I have mentioned this to a few of my fellow engineers over the years and they have looked at me like I was speaking ancient Aztec" This person ran it by some colleagues, who all disagreed, and the author took this as evidence in FAVOR of his belief? The hubris...
- thrown_22 4y ago>Stop being a crotchety and elitist angry person and try to understand the way things are going, instead of casting new methods aside because you don't personally understand or get them. Simpler methods are more robust than more complex methods. For example: https://www.rsc.org/images/Arrhenius1896_tcm18-173546.pdf https://www.rsc.org/images/Arrhenius1896_tcm18-173546.pdf predicted climate change more or less as it happened a more than a century ago. The current models are hugely complex and not that much more accurate because we're trying to simulate a system with a lot of unknowns. The same is true just about everywhere when you start running ensemble simulation for multiple inputs. No one does because "We have 20% of simulation end up at infinity or 0" is not a very meaningful statement.
- ska 4y agoYou're both partially right. There are things you can do efficiently now with modern simulation that would be unthinkable in the heyday of the slide rule. Hell, in the 1980s. On the other hand, I've seen a lot of time wasted on "analyzing" the wrong things, especially via simulation, merely because the work of setting it up is very approachable. I've watched young engineers struggle hard due to an over-reliance on these approaches, so it isn't just crotchety-old-guy problems. Its' also that, though :)
- salty_biscuits 4y agoI agree, it is an old man rant. It is funny the lack of insight people have in their own intellectual journey. When you are a neophyte, of course all the old guard have all this intuition that you admine. Then when you are experienced every one around you doesn't seem like they know what they are doing. It's because you got better you clod, not that they got worse. Those people you admired when you were inexperienced wondered the same things about you when you didn't know what you were doing.
- tibbetts 4y agoI dunno, I watched two professional architects not be able to estimate a beam size for a 16’ span without mocking it up in autocad. This delayed us like a week in design iterations, and cost me probably $2000 in architect hours. I own a book inherited from my grandfather that just told me the answer. A 72-year-old architect who helped with a later revision of the project also knew the answer off the top of his head. That’s not to say I would build the house without doing a proper structural engineering analysis and simulation. But not being able to estimate feasibility without doing the full simulation is a real problem.
- bee_rider 4y agoA 72 year old architect is a person who's decided to keep being an architect after all these years. I bet in 1980, you could find 30 year old architects who would take a week to figure that out. They've just gone into management or retired by now.
- deleted 4y ago[deleted]
- onos 4y agoYour critique may be fair, but I appreciate the perspective that laments lost mastery of old methods and tools. Although it’s true that many today are proficient in the old math methods, nothing beats using it day in and day out. The new may be better, but that doesn’t mean something else that was also good was not lost here.