↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

How to Manage Programmers Without Losing Your Damn Mind

The post says managing programmers is hard when managers do too much of the thinking, drift into advice-giving, and end up exhausted without making real progress. Its main remedy is coaching: ask better questions, help people define the real issue, and let them solve more of the problem themselves.

Reading notes
#

  • Managing programmers often leaves managers overloaded, off track, and tired because they try to do too much of the work themselves.
  • Solving problems for staff can make them dependent on the manager and turn the manager into a bottleneck.
  • The book the post summarizes uses seven essential questions to shift the manager from advice-giver to coach.
  • Coaching for performance solves the immediate problem, while coaching for development builds problem-solving skill and confidence.
  • “What’s on your mind?” is the opening question, and it can be softened with “out of curiosity.”
  • If the answer is vague, the post suggests looking at the project, the people, and the patterns.
  • “And what else?” helps slow the conversation down, surface more options, and keep the manager from jumping in too early.
  • “What’s the real challenge for you here?” helps move past lists, complaints about third parties, and abstract talk.
  • Questions starting with “what” are preferred because “why” can put people on the defensive.
  • “What do you want from me?” helps the manager avoid guessing what the other person wants.
  • The post uses the drama triangle to describe the victim, persecutor, and rescuer roles managers can slip into.
  • It says people need to feel safe in conversation, and names tribe, expectation, rank, and autonomy as factors that shape that safety.
  • Silence matters after a question, and the manager should not rush to fill it.
  • “How can I help?” pushes the other person toward a specific request and keeps the manager from assuming the solution.
  • When someone asks directly for advice, the post recommends first asking what they have already thought of before offering ideas.
  • Saying yes to something also means deciding what to say no to, including projects, expectations, habits, and beliefs that must be deprioritized.
  • The post says the secret to saying no is often to say yes more slowly and ask more questions before committing.
  • “What was most useful to you?” closes the conversation, gives feedback, and helps the other person remember what was discussed.
  • The writer says the book was useful because their own habit of jumping into advice mode was not helping anyone.