Skip to content
#Management

How to Take Great Engineers & Make Them Great Technical Leaders • Courtney Hemphill • GOTO 2017

#Management #Software #Processes #Project #ProductManagement #Engineering #Leadership #Staff #Architecture #Career

Interesting. speech Technical leaders who have been around for many years:) The author often mentions various sources and the audience has never heard about them – seven years ago I did not know about many of them, but by now I have read all the books and studies that the author mentioned. The presentation structure is very good. The author talks about the things that matter to tech leaders that grow out of an engineer.

  1. Communication (general management 101) Here the author talks about the correct approach to writing documents from Barbara Minto.pyramid principle", where it is necessary to start with the answer to the main question, then to give supporting arguments, and then to give facts and data. Barbara came up with the SCQA approach to storytelling: situation, complication, question, answer. And then the author moves on to goal setting and talks about OKR. (objectives and key results) Andy Grove. 2) Culture Here the author recalls Project Aristotle from the guys at Google (me told about)The main factor of effective teams at Google is psychological safety. You can also read about the generative culture of Westrum. (me told about). The author also notes the importance of mentoring both inside the company and with people from outside. And ends pairing:) 3) Authenticity (be a human) Here the author talks about radical honesty. (radical candor)and the use of retrospectives. 4) Paths (dual track leadership) There are two development tracks: engineering management and individual contributors. The opportunity to grow not only as a manager but also as an engineer. We mean it. communicate With my colleague, Lesha Tarasov, in the sixth issue of Code of Leadership about Staff+ engineers.

P.S. The author gives interesting metaphors between the engineering part and the management part.

  1. Open Source -> Writing
  2. Continuous Integration -> OKRs
  3. Test Driven Development -> Psychological Safety
  4. Pair Programming -> Mentorship
  5. Code Reviews -> Radical Candor
  6. Regular Refactoring -> Retrospectives

#Management #Software #Processes #Project #ProductManagement #Engineering #Processes #Leadership #Staff #Architecture #Career