[5/8] Managing Humans: Biting and Humorous Tales of a Software Engineering Manager (How to Manage Intellectuals: I'm Nerds & Geeks) (Category Management)
I continue the story of this book with a review of the third and last part of Versions of You, where the author talks on his fingers about the geek mindset and how to successfully learn with different people, where each person is a different version of you:) Posts from other parts of the book are available here 1, 2, 3, 4.
32) Boring people quitting There can be many reasons for dismissal, but not everything can be influenced. But boredom is an important factor and one that can be dealt with. It's worth doing something like this.
- We need to track employee boredom. Let them work on interesting tasks.
- Allow experimentation
- Sharing a shitty job equally. (It's not just throwing everything away for one lucky guy.) Eliminate external noise and unnecessary interruptions Share information and show a big picture Well, you should not forget how to develop software and write code to stay with your employees on the same wavelength and see their problems.
33) Leaders. How to test skills in interviews with assistants (leader)To help ask for technical skills, cultural fit and check your mindset (strategist). At the end, a general final meeting should be held and a hiring decision should be made.
34) Interview length in 90 days An interesting chapter about your actions on probation and tips that will help you pass it successfully. All of them. 8 pieces Leave later and come early - pay attention to other people's work schedules Accept all invitations for lunch from colleagues Always ask for clarification of the abbreviations.
- Say something really stupid. (You’ll still do it, even if you don’t plan to.) Have a drink after working with colleagues. Tell someone what to do will test your understanding of the situation. Argue to understand how the company treats conflicts
- Find your narrow circle. But know that your interview won’t end until you change into a team.
35) Guide geeks The author suggests thinking about what is important for geeks and continue to use it in their management.
- Geek thinks systematically.
- Geek values permanence.
- Geek values efficiency. In the end, geek time must be protected. In addition, the author gives the concept of 2 vertices for a geek.
- Top. 1 a specific node that needs to be untied to solve the problem
- Top. 2 Why do nodes exist and how to make a system without them Top 1 - it's a regular job, and the top 2 It's something revolutionary and some kind of "click" and a new level of understanding. We need to make sure that geeks have the opportunity to catch this "click"
36) Attention syndrome in geeks The chapter on ADHD, context switching and information absorption is important for efficiency to choose a mode of the day. The author separately notes that the younger generation of ADHD is more common:) 37) Geek in his cave In order to get into a state of flow, special conditions are needed. The author calls “cave” the place where these conditions were achieved. In fact, this is a geek's "house" in which it can be effective.
Continuation in the following posts.
#Management #Software #Engineering #SoftwareDevelopment #Processes #Leadership