![Daniel Markham](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="48" height="48"><rect fill-opacity="0"/></svg>)
I am begging software people to talk to a single traditional engineer
![I think that the difference between e.g., mechanical engineering and software engineering are perceived the way they are BECAUSE of the immaturity of software. Mechanical engineering was able to move past a certain point because rather than having to hammer out their own, engineers discovered the One True Nail, or the One True Lockwasher, or what have you. The same is not true of software, at least not yet.](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="810" height="137"><rect fill-opacity="0"/></svg>)
Thread
Conversation
Replying to @hillelogram
![Daniel Markham](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="73" height="73"><rect fill-opacity="0"/></svg>)
Reply
Reply
Replying to
(If you don't know any traditional engineers, you can instead read my project on this, where I interviewed 17 people who moved from trad to software)
1
10
74
Replying to
> one true fastener
how many people stripped a Phillips head screw in the past five minutes? I bet it's a lot
...hm, if I were a sociopath and still a manager that'd make a great bad interview question
3
41
That’s how you filter for hiring Canadians and others with good taste, just see if they immediately go on a rant about Robertson
4
Replying to
I, um, what? The difference is that mechanical engineers are asked to build one product that does one thing really well.
And software engineers are asked to make something that does everything, can be changed at a moments notice, and is changed several times in its development.
1
13
> I, um, what? The difference is that mechanical engineers are asked to build one product that does one thing really well.
You'd be surprised! mechanical engineering is at times just as messy as software engineering is
(chem engineering is a bit closer to software, too)
1