3 ms·
My biggest win, mentoring: a new guy put in charge of 'Engineering data' e.g. putting ad-hoc document solutions under one umbrella. He was worried, not an Engin
by JoeAltmaier 7y ago
My biggest win, mentoring: a new guy put in charge of 'Engineering data' e.g. putting ad-hoc document solutions under one umbrella. He was worried, not an Engineer, thought he'd make a fool of himself. I said "Here's the trick. If you don't know something, say out loud "I don't know what that means. Can you explain it to me?" And because Engineers usually are happy to explain their shit, they'll not think badly of you but instead become helpful. Never bluff or fake it.
Fast forward 2 years. Everybody now respects him. He's the most generally knowledgeable guy in the company, the CEO consults him. Moved to manage the new products. He's on the road to Director now. Still the same helpful guy with the reassuring voice and the insistence everybody in the room understand before moving on.
- ChrisMarshallNY 7y agoLove that story. Thanks for sharing it.
- ignoramous 7y agoYou'd like this related discussion from way back when on https://42floors.com/blog/startups/i-dont-know https://42floors.com/blog/startups/i-dont-know: https://news.ycombinator.com/item?id=7334671 https://news.ycombinator.com/item?id=7334671
- Igelau 7y ago> Engineers usually are happy to explain their shit Ain't that the truth. Get us going and you'll have to beg us to stop.
- folkhack 7y agoThis, and I hate putting someone in a situation that they don't know up from down... Even with the "highly opinionated framework" thing you still get lots of variation on how things are built, and my products are no different. I find people are much more immediately capable if I can get a 1-2 hour "nuts-to-bolts" meeting to cover the bases. Also gets the mojo going for good questions as well.
- pault 7y agoI always give this advice to juniors and stakeholders. If you bullshit an engineer they can smell it from a mile away and they'll never respect your opinion again. If you tell them you don't know, you'll get an hour of expert level education on a subject for free.
- jerf 7y agoSomething I say to every new employee on their day one is: "I expect questions. I will come looking for you if you don't have any and ask you why you don't." Because even if you know all the tech stacks we're using inside and out, which I don't believe, you still won't know our own local quirks. Everyone knows you don't know; don't be the last to that party.
- monadic2 7y agoOn one hand, I really emphatically agree with this sentiment. On the other hand, this post comes off as almost a parody of self-improvement advice.
- JoeAltmaier 7y agoI'll let Cliff know. For him, it seemed to work out ok.
- deleted 7y ago[deleted]
- monadic2 7y agoThe advice is fine, but it comes off as disingenuous to extrapolate a single anecdotal example so confidently without articulating the basis for your confidence.
- WalterBright 7y agoIn my first job, I discovered my boss had an encyclopedic knowledge of chip pinouts. So when I needed to know a pinout, I asked him. One day he blew up at me and said I had a TTL data book on the shelf and to quit wasting his time because I was lazy. He was absolutely right! It's good to ask questions, but not before RTFM.
- BHSPitMonkey 7y agoI wouldn't describe that as being "absolutely" right. A team is more productive when its individuals' strengths are pooled together, and there's no sense in refusing to make use of a specialist's skills (within reason). Yes, you want people to learn and become more self-sufficient over time, but not at the cost of finishing projects in double the time.
- WalterBright 7y agoConstantly interrupting a specialist when you could instead pick up the data book is abusing him.
- ChrisMarshallNY 7y agoDepends. It was “the boss.” If they are a critical-path engineer (which, in my experience, is a very bad idea for managers), then they shouldn’t be used as a StackOverflow board. However, if they are a true manager, then they work on “interrupt,” anyway, and their quick answers may improve the performance of the team, which is really Job One for any manager. I say this, having been a manager for many years. It sucked. I hated it, which is why I am pivoting back into engineering. I was a damn good manager, though. If you go to my LinkedIn profile, you’ll see lots of testimonials from former employees. One reason I was good, was because I kept myself out of the critical path.
- mandelbrotwurst 7y agoI generally agree with you here, but there is still a limit to what extent and over what it is reasonable to interrupt a manager - given enough interruptions, they won't have any capacity left over at all!