by Naac on 2/2/22, 10:47 PM with 110 comments
by JackFr on 2/3/22, 3:00 AM
Of course I could be wrong — consciously or unconsciously I could simply be voicing my own bias. But I think at some level people prefer a simple narrative with a hero and a villain regardless of whether the narrative is true.
by dustintrex on 2/3/22, 1:02 AM
by BurritoAlPastor on 2/3/22, 12:19 AM
However, if I were to decline to speculate on any matter on which I lacked an expert-level understanding, the number of subjects on which I could hold a conversation would dwindle to virtually nothing, and I'd be much more boring to talk to at these cocktail parties. So, I intend to continue to spitball blindly, just for fun.
by emtel on 2/3/22, 12:32 AM
What I think would be more interesting is the question: when are outsider critiques or suggestions likely to be valid? To stay with the construction example, it is clear that construction in the US is more expensive than it needs to be in many cases - railroad construction costs are famously many times higher in the US than in other industrialized countries. Is there insider knowledge I don’t have that would make this observation fallacious?
And what about cases where one isn’t simply pointing to a counter example? Are there cases where outsiders have made arguments from first principles that were correct, despite their lack of expertise in the field?
by acrump on 2/3/22, 9:07 AM
"At last I went to the artisans, for I was conscious that I knew nothing at all, as I may say, and I was sure that they knew many fine things; and in this I was not mistaken, for they did know many things of which I was ignorant, and in this they certainly were wiser than I was. But I observed that even the good artisans fell into the same error as the poets; because they were good workmen they thought that they also knew all sorts of high matters, and this defect in them overshadowed their wisdom"
https://www.sparknotes.com/philosophy/apology/full-text/apol...
by exolymph on 2/2/22, 11:56 PM
by Avalaxy on 2/3/22, 1:28 AM
by vincentmarle on 2/3/22, 12:18 AM
This is exactly why I moved away from SF. Can't stand these alpha nerds trying to one-up each other at parties.
by dahart on 2/3/22, 1:13 AM
My local Department Of Transportation has this notice on the info page of the bridge construction project nearest to me:
“This is a design-build project, meaning the design and construction will happen simultaneously, which allows DOT and the contractor to include the most innovative and current construction solutions while ensuring a quality product.”
by friedman23 on 2/2/22, 11:35 PM
by wink on 2/3/22, 10:26 AM
"How long will it take to implement search here?" "Wait, why does it take longer than a week, Google can do it".
Things I've heard an actual Product Owner once say. Please tell the the one automobile engineer who was asked to make a car in a week.
So yes, I absolutely believe that /some/ programmers will say that their work is so complicated and like engineering, there are just a lot of seemingly exaggerated examples that have actually happened. I'm not saying it's harder. I'm just saying there are classes of problems that should not happen in civil engineering.
Project is halfway done, written in Python. Someone: "Can we not switch to Java?". I would equate that to "The metal bridge is halfway done, can we switch to wood?". This is not inferring that this is the most concerning problem in a problem, and that's my gripe with this article. And the moving bridge is also an exaggerated example taken for shock value. How often does that really happen? And would you put a random engineer of medium seniority in charge of this?
Disclaimer: I am not saying programming is harder or special. I've worked on construction sites and I've seen my fair share of ridiculous requests. But people are often simply persuaded a lot easier if you point to a physical wall and explain the problem, versus software where you need to start explaining at the very beginning. Sadly, often also for customers or product managers.
by supernova87a on 2/3/22, 4:19 AM
If an executive with some great new idea or strategy not grounded in the full detail were to pay attention to the all the details, they might never try or get anything new done. Because if you listen to and empathize with all the details of how complicated something is and how there's this subtlety or that follow-on issue, you start to accept all the reasons it can't be done (either at all, or quickly). So in some cases, you only get progress because of persisting in ignorance that you can do something new that breaks the rules.
Of course I don't mean doing something that is structurally or physically impossible -- just in cases where the legacy of "why it can't be done" has created inertia that stops progress if you accept it a little too much.
by Hermitian909 on 2/3/22, 2:48 AM
by matsemann on 2/3/22, 11:09 AM
Heh, I also disagree with this quote, but for a different reason than the author. I mean, what's nice about CS is that's it's pure, deterministic, straight forward. It's like doing basic physics problems and the text states "assume zero air resistance and zero friction". We have the simple laws of physics.
I don't envy those having to deal with the messiness of the real world. They have it far harder than me as a programmer.
by tompccs on 2/2/22, 11:47 PM
This cocktail party observation is definitely common in certain circles, but I think particularly American culture, where maverick thinking is so highly prized. This type of thinking is a true wellspring of innovation, but is not accessible to the vast majority of people. It does remind me of this xkcd: https://xkcd.com/675/
I'd also caution against being too harsh in such people, especially in informal situations. "Why don't you just..." type questions are actually a great way to improve your understanding of a field, and should be taken in the spirit of curiosity, and not necessarily as an indicator of extreme hubris.
by dfan on 2/3/22, 12:35 PM
by gnicholas on 2/3/22, 2:52 AM
https://www.amazon.com/Scout-Mindset-Perils-Defensive-Thinki...
by imwillofficial on 2/3/22, 2:10 AM
by midenginedcoupe on 2/3/22, 11:30 AM
by crsv on 2/3/22, 12:48 AM
by cycomanic on 2/3/22, 7:18 AM
Unfortunately it became soon apparent that the execs mainly had "cocktail party ideas" about changes, "we created a new business in this area that didn't exist before, which is much harder than running an established business. therefore we know best. How hard can it be". So the production manager and my friend soon became the naysayers because they said when they thought things wouldn't work. Soon after they both were made redundant, but the business is now very close to going under.
All this story just to say, that this is not just at cocktail parties, but also in work situations people like to discard established knowledge because they think they know how to "disrupt" .
by sampo on 2/3/22, 8:47 AM
"Sometimes the Best Ideas Come from Outside Your Industry"
https://hbr.org/2014/11/sometimes-the-best-ideas-come-from-o...
by soheil on 2/3/22, 3:48 AM
by spirographer on 2/3/22, 7:57 PM
by MattGaiser on 2/3/22, 12:47 AM
That is the incredible thing about Silicon Valley. People who knew/know nothing about various industries when starting come to utterly dominate them.
Amazon should never have succeeded. They knew nothing about books compared to booksellers. They won anyway. And then proceeded to utterly crush every other company in retail. And they continue to do so.
SpaceX is utterly absurd in its existence. Utterly absurd. Boeing and Lockheed had way more knowledge and experience. Yet they are about to be pushed out of a lot of launch.
by rq1 on 2/3/22, 3:04 AM
by Isamu on 2/3/22, 1:38 PM
Doesn’t take long to find something that can change your views or offset your ignorance.
by andmarios on 2/3/22, 1:52 PM
Also, whilst it is intuitive that someone without expertise in a field is easy to get everything wrong, it is more interesting that often experts also get everything wrong. Sometimes this happens because the problem may affect an expert's field but belongs to another field, or the problem just exists from someone else's point of view.
In Greece we refer to people who always know everything better than experts as couch coaches. :)
by gundmc on 2/3/22, 4:29 AM
by bradleyjg on 2/3/22, 4:19 AM
I’m exchange I’m happy to listen to civil engineers and construction workers theories about why Tesla is taking so long to deliver the full self driving software they’ve been charging for.
by nikisweeting on 2/3/22, 6:55 AM
by eyelidlessness on 2/3/22, 4:00 AM
I don’t think this is fun at parties.
by throwawayarnty on 2/3/22, 1:26 PM
And as more and more information is distilled into sound bites, tweets, and simplified visualisations, I am afraid more and more people will spend their brain power acquiring little bits of knowledge, never going deeper than a 10-minute TED talk.
The end result will be great cocktail party conversations, but very few people actually solving real problems.
by raldi on 2/3/22, 8:07 AM
by chrisseaton on 2/3/22, 12:12 PM
by Malic on 2/3/22, 1:39 PM
by jiveturkey on 2/3/22, 10:37 AM
by TameAntelope on 2/3/22, 4:37 AM
In my more charitable moments, I think that it's good mental exercise, but it's hard to think generously about someone else when you hear them say superficial "I could do better" statements like the topic of this article. How could they be so naïve, to think that they can, casually, upend an entire field? It happens on Reddit (and HN) all the time, too. Every community centered around a creative work is lousy with, "Why didn't they just" style arguments.
Also, not for nothing, but I've never heard the "building an airplane while flying it" analogy used to suggest software is harder than building an airplane. Pardon my cursing, but who the fuck thinks programming is harder than aerospace engineering???
Finally, I found this super duper hard to read all the way through, due to the lack of formatting. I'm assuming that decision is somehow intentional, but it's not a kind one. My eyes hurt. :(
by transitivebs on 2/3/22, 2:24 AM