Hacker News Reader

Comment by kevindeasis | Hacker News Reader

Hey there I teach people to code some of them I teach web.

I think the easiest way to go about this, is to learn how to fly a plane. Then once you've learnt that you can kinda learn it piece by piece. IE: it's easier to teach someone how to drive a car first before teaching them how to mod it and write a self-driving program for it.

But, then again, some mechanical engineers learn how to build planes, before knowing how to fly a plane.

It really helps if you can reach out to someone in that industry and they can show you the ropes

View on HN

My first day on the job at Boeing, in the 757 flight controls group, as a newly minted mechanical engineer, my lead engineer told me to "size the jackscrew". The jackscew is what drives the leading edge of the stabilizer up and down. If it fails, the airplane becomes uncontrollable.

I went back to my desk, stewed for a while, and panicked.

So I go back to Erwin, shamefaced, and said I had no idea how to size the jackscrew. He chuckled, and said "did they teach you column buckling in school?" I said sure. He said it's a column buckling problem. You know how to do it.

And sure enough, I did.

Nothing to be ashamed of there. You hadn't had enough domain specific exposure to cut through the jargon from the sounds of it. First exercise I do with my hires/juniors is work to connect what we're doing with something they already know.

That's communication 101.

201 is divesting yourself of the assumption you always know exactly what everyone else is talking about, and remembering that it never hurts to play the fool and learn something, as in the process of being taught, sometimes new knowledge will become apparent.

People who master both pieces tend to be the most amazingly competent people I've ever had the privilege to work with.

OOh, ooh, ooh, me too!

A couple months into my first job, the chief engineer, who was an ME in an EE company, told me to figure out how a certain filter worked. I sat down at my desk with the diagram for hours struggling with it. Then I got up to go to the bathroom or something and came back in through a different door and saw the schematic upside down and that from that perspective it looked totally different. It was just a 2-port network; I know all about 2-port networks!

A few minutes later I was done :-)

Reply on news.ycombinator.com