In this episode, Dave and Jamison answer these questions:

1. I recently started listening to your podcast from the very start of the show! One of the largest differences I noticed (aside from the audio quality, lol), is how often you used filler words like “um”. How on earth did you manage to stop using them? In work presentations and demos, I often end up using the filler words, and listening to the recordings later is painful. The rehearsed parts of the presentation go smoothly, but as soon as I go out of the “script”, I start depending on filler words. How do I get better at this?

2. How exactly should spikes go? I’ve done some deep dives to understand the scope and steps of an upcoming effort, all with detailed write-ups, only to later realize during the implementation that I got some things wrong or missed out some important details. Isn’t that the point of a spike, to root out any unknowns or surprises? Short of just doing the actual implementation, which I’m pretty sure is also missing the point of a spike, What am I doing wrong and how can I properly present post-spike findings to my team?

In this episode, Dave and Jamison answer these questions:

1. My architect is too busy with his kids! His kids have had a lot of school and medical issues over the last few months and he’s ended up flexing a lot to take care of them. This causes meetings to get rescheduled or scheduled far out in the future, which is contributing to timeline delays on some large projects that need more attention.

   I don’t want to be rude and insist that he put the company above his family, but he needs to be driving organizational alignment, not his kids! I’m stressed out by not knowing when he’ll be available and having to do extra work or take important meetings without having him as backup!

2. ‌

   Can you help me understand what happened here? I was put on a ‘performance improvement plan,’ and it became pretty clear to me from the negative feedback at my first review that I simply didn’t have the skill to perform at the level that was being asked for. Instead of immediately looking for a new position, I decided to take some personal time off to work on myself and my mental health, and to use the remainder of the performance improvement plan time to prepare myself emotionally and financially for that. I didn’t blow off work, but I also wasn’t invested in the performance improvement plan either. A few days before my final review, I quit instead of being terminated. Management seemed really confused and angry when I quit. Why would they be so upset if they were about to terminate me anyway? One in particular started backtracking and pretending like I wasn’t going to be terminated.

In this episode, Dave and Jamison answer these questions:

1. I work at a startup that makes embedded devices and the software that runs on them. Everyone on the tech team does both. We recently hired someone to lead the tech team to give the CTO more time for other duties. My new boss is incredibly experienced with hardware design and embedded systems and has been in the industry for a long time (40+ years). However, they are not familiar with modern software practices like version control. They will frequently ask us to do things like delete all copies of a broken version of software. When we try to explain how git works they will ask us to make a new repo with the now working version of the software even if the fix was a 1 line change. How can I politely explain that they just don’t understand how this works and correct them without being rude?

2. What’s a “normal” rate of performance firings on a team/engineering department? I recently got a new job at a growing startup, and it’s fairly uncomfortable seeing the ghosts, on messaging apps and docs, of like 6 people in the ~25-person department who’ve been fired in the last half year. With that said, the department is continuing to hire, so I don’t think this necessarily means I should be worried. But does that sound like an unusual amount of performance-based firings?