In this episode, Dave and Jamison answer these questions:

Questions

1. How do I incentivize people to maintain documentation?

   Getting anything done at this large enterprise company is a massive challenge because documentation is constantly out of date and people only have half the information needed. So much time gets wasted because people have contradicting knowledge about the status of projects, systems, or requirements.

   Should I just quit my job or can this be fixed?

2. Greetings! First off, great show - thanks for the countless episodes, most of which result in me getting weird looks as I chuckle to myself while running and listening. I have a passion for technology which lead me to a career in development. I am very often researching new languages and software that will help us do our jobs and/or lives better in my free time. I get excited about these things I find and want to share them with my co-workers but often get rebuffed by them, asking me why I spend my free time “working”. I know I can’t expect everyone to share my enthusiasm and passion for this stuff, but I am finding it discouraging being on a team where this curiosity is not celebrated/encouraged. I love the company I work for and don’t want to leave, but I find myself becoming more and more disconnected from my team because of this. Any suggestions on how I can share my passion with my co-workers is a way that is mutually beneficial to me and them? Thanks, keep up the great work!

Show notes

Gary Bernhardt’s WAT video from 2012: https://www.destroyallsoftware.com/talks/wat

In this episode, Dave and Jamison answer these questions:

Questions

1. I’m not a developer, and have never worked with developers. I have four years of systems/IT experience (ansible, bash, python, windows, etc). I got hired in a devops role at a company with many developers. How can I make sure I’ll have meaningful discussions (and a good learing experience) with software developers in my upcoming devops role at a new company? Will they notice that I don’t know what an enterprise communication bus is if just don’t ask but instead scribble something in my notebook?

2. I just watched “How to crash an airplane” by Nickolas Means. It is about how the flight crew of an airplane crashed in 1989 yet saved 189 lives. The learning is that there are no heroes and teams can succeed only with inputs from all members in the team. All opinions need to be heard. And he also emphasizes that the captain used “we” in all his speeches.

   When it comes to interviews, the expectation is to talk about your personal experience. Using “we” during interviews would look like negative, right? Especially in leadership interviews, this is difficult since leaders are successful only with their team.

   Can you give us some strategies to balance this the best?

In this episode, Dave and Jamison answer these questions:

Questions

1. I’m a Tech Lead at a decent sized corporation. If I want to grow towards a promotion my options are a more people management track towards Engineering Lead (basically a TL who also manages 1-2 other TLs) or a more technical track towards Staff TL. Where I’m struggling is I don’t know how I would actually work towards the Staff level, seeing as most of my time is spent wrapped up in mentoring, coaching, planning meetings, and just generally large blocks of time spent on Zoom. Have you ever seen someone move down that path? I worry I would be letting my other responsibilities slip through the cracks by focusing on my own technical advancement. How should I balance what my team needs from me vs. what I need to focus on to get to a role like that? Is the best way to get there 1 step back (to being an individual contributor again) and then two steps forward (working towards Staff Engineer then Staff TL)?

2. Hello soft skills! Love the show and your great banter, keep the laughs coming.

   Do you have any tips for ‘active listening’? My manager is very, very chatty and our catch ups over zoom often last two hours or more. I find myself drifting in and out while he talks and then need to snap out of it when I hear something that might be useful.

   How do I keep focused in extra long meetings where we are one on one and the content is not particularly interesting?

   Thanks!

Show Notes

https://mediocre.dev/it-takes-more