Travis and Brandon talk about how teams can support early-career developers and career changers. What environments are they a good fit for? How do you set expectations for newer folks? How can you help them get and stay productive? Is the cost of doing so worth it?

They also talk about the surprising lack of definition around the space between "Entry-Level" and "Senior" engineers to define the main role that the rest are supposedly based on. They talk about the Dreyfus model of skill acquisition, how folks get stuck in "Advanced Beginner" stage, and how to help them move to "Competent" and toward real, holistic expertise.

Notes:

• Zone of Proximal Development
  • https://en.wikipedia.org/wiki/Zone_of_proximal_development
• Charity Majors tweet
  • https://twitter.com/mipsytipsy/status/1191622396207190016
• Bryan Liles tweet
  • https://twitter.com/bryanl/status/1192408098457174016?s=21
• Dreyfus model of skill acquisition
  • https://en.wikipedia.org/wiki/Dreyfus_model_of_skill_acquisition

Travis, Nick, and Brandon discuss a tough-but-frequent listener question: "How do I coach senior developers and tech leads to work better with each other when they have opposing personality types or passions?" They explore the personality types of "ship it" vs. "perfect it". Brandon talks about what happens in the 1 out of 5 times when the conflict is ego- and control-driven rather than just slightly different values (hint: it's not great news). They discuss techniques to draw out the benefits of these personality differences to lower drama, build trust, and balance a team's ability to focus on outcomes with technical and product excellence.

Notes:

• Your high bar is wrecking your team
  • http://brandonhays.com/blog/2018/06/19/your-high-bar-is-wrecking-your-team/

Nick pays homage to one of his heroes, Captain Al Haynes, who saved hundreds of lives by managing a crisis during a famous airplane crash. Captain Haynes demonstrated one of the canonical examples of Crew Resource Management and "just culture". They ask why we still adhere to the "unquestionable captain" myth and point out some of the (very public) disasters that created. Nick talks to the group about how he pivots into "questions/curiosity" mode from "assumptions/making a point" mode. They discuss the impact and legacy of Captain Haynes and how that's impacted the way we choose to lead and live.

Notes:

• Capt Al Haynes
  • https://en.wikipedia.org/wiki/Al_Haynes
• Crew Resource Mgmt
  • https://en.wikipedia.org/wiki/Crew_resource_management
• United 232
  • https://en.wikipedia.org/wiki/United_Airlines_Flight_232
• United 173
  • https://en.wikipedia.org/wiki/United_Airlines_Flight_173
• Tenerife airport disaster (worst air disaster)
  • https://en.wikipedia.org/wiki/Tenerife_airport_disaster
• Turn the Ship Around!
  • https://www.amazon.com/Turn-Ship-Around-Turning-Followers/dp/1591846404

Travis, Nick, and Brandon talk about vacations after a summer full of them. When is it OK for managers to take vacations? How do you set things up to actually let yourself relax? What if something breaks while you're gone? Nick talks about the power of asking "When's the last time you took time off?" and how to clearly set the cultural expectations in "unlimited PTO" policies. The group discusses vacations as part of an overall self-care strategy.

Notes:

There is a healthy and active debate in the management community around Manager READMEs. Are they self-indulgent excuses for asking people to "deal with" your shortcomings? Or an essential tool to guide future conversations? Nick and Brandon explore the nuance in there and how their views about Manager READMEs have evolved (and continue to evolve) as they're exposed to more examples of them in practice.

Notes:

A thread on the "orange website" got Nick thinking: What are signs a manager is succeeding? What are red flags that they're on the wrong track? They ask the big question: How do you know when you are doing a good job? Are there any actual, useful measures you can use to know a manager is effective? And once you have an idea of what success looks like, how can we help scale that across an organization?

Notes:

Nick, Travis, and Brandon explore trust as a pillar of successful teams. What does a high trust environment look like? How do you build trust? How do managers accidentally lower trust on their teams? How do you build (or rebuild) trust between a team and the rest of the organization? They relay the "marble jar" metaphor and explore what that means for teams.

Show notes:

This week, Nick, Travis, and Brandon respond to a listener's question about when and how to successfully use performance reviews. Nick shares the idea of using "pattern matching" as a basis for evaluating performance. They discuss whether to tie performance to raises, and how to gather and provide feedback outside the performance review process.

Notes:

Nick, Travis, and Brandon explore how they've tried to improve at assessing the technical abilities of potential hires during the interview process. They talk take-home tests, pair programming exercises, and Nick shares a technique that has worked better for his teams than either of those.

Notes:

Travis, Nick, and Brandon talk about Rule #1 in running software teams: The Software Must Ship. How much of that is on you, the manager? They explore that question and talk about their experiences managing work backlogs, delivery cadences, and giving teams slack to help them go faster.