> A line I often hear from programmers is that programming is like "having to build a plane while it's flying", implicitly making the case that programming is harder than designing and building a plane since people who design and build planes can do so before the plane is flying1. But, of course, someone who designs airplanes could just as easily say "gosh, my job would be very easy if I could build planes with 4 9s of uptime and my plane were allowed to crash and kill all of the passengers for 1 minute every week".
We tend to think that some problems are only as complex as our understanding of them.
That condition has a name, and it is "Engineer's Disease" or "Engineer's Syndrome."
Even if that's the case, I think framing it as "Engineer's Disease" is pretty critical for HN, which at times can become a literal orgy of it.
Also, SV culture amplifies Engineer's Disease into a destructive force only rivaled by its counterpart in finance. Doctors and lawyers who suffer from something similar are far more limited in their effects.
I think that's kind of missing the point. Also, I don't think many doctors are making the switch to engineering. Why would they? There are probably far more engineers becoming doctors than vice versa (though the total numbers in both directions are likely small).
The specific problem with Engineer's disease, is that engineers have the job of building things for others, and thus have the opportunity to force their half-baked ideas onto them. SV has amplified that and turned it into a monster, by elevating things like "disruption" into something like a moral imperative.
The counterpart in finance and the closely related managerialism rival it because those jobs involve control of others.
Doctors though? If they get arrogant about some other field, they usually just end up hurting themselves or a few others (like they learn to sail, get in over their heads, and sink their ship in a storm). They don't have a mechanism to do more damage.