It takes more than great code
to be a great engineer.

Soft Skills Engineering is a weekly advice podcast for software developers.

The show's hosts are experienced developers who answer your questions about topics like:

  • pay raises
  • hiring and firing developers
  • technical leadership
  • learning new technologies
  • quitting your job
  • getting promoted
  • code review etiquette
  • and much more...

Soft Skills Engineering is made possible through generous donations from listeners. A heart with a striped shadowSupport us on Patreon

A speech bubble

Why should you listen?

Here's what listeners say:

Recent Episodes

Latest Episode

Episode 435: How to make my boss actually do something and kindly shooting down

Download

In this episode, Dave and Jamison answer these questions:

  1. First! I recently listened to episode 178 (huge backlog of episodes to work through!) and Dave made the assertion (in 2019!) that 47% of all companies would be remote by 2023: wildly close, what else do you see in the future?

    Second: my work situation continues to confound and external insight would be helpful! My boss and I have a long working history going back to an entirely separate company. I’m a high-ownership/high-drive Principal level IC and feedback has been lackluster. Takeaway from last years performance review would be best summarized as “I agree with your self review. End message.” I’ve been working to “manage up” and mentor (reverse mentor?) him, but he always makes snap decisions and then refuses to reevaluate after presented with more info. Coupled with his myopic view of our team’s scope and general preference for speaking only (not much for action), I’m trying to figure out how to get where I want to be without burning an old and historically very useful bridge! I want to work on big technical problems, instead I’m de facto manager of a team… I managed before and did not enjoy being responsible for people. As a principal I’m responsible for their output somewhat, but if they underperform I work with their manager and them to prioritize, and do up front work to incentivize their investment in what we’re doing… help!

  2. What do I do when my teammate proposes a new architecture or framework in a new project? It might solve some existing problems but has a high chance to create technical debt and make the onboarding harder for new engineers.

    How can I convince them to use the existing solution while still helping them feel comfortable sharing their opinion next time?

    If I follow their suggestion but things don’t go well, how can I convince them to refactor the structure without them feeling like I’m blaming them?

A smiling speech bubble

Episode 434: Forgetful boss and nothing to say

Download

In this episode, Dave and Jamison answer these questions:

  1. My boss has been forgetting a lot of stuff lately — decisions from team discussions, action items from meetings, their own decisions that they then go against later, etc. They’re great overall, and this is definitely just a human thing… we’re not perfect. But how can I help them remember or remain accountable without feeling like the snitch from “Recess”?

  2. Listener Gill Bates,

    Hey! I started working in a big tech company recently and I feel like I am on a different planet all of a sudden. Before, I did only work in startups and small companies. I have joined as a senior developer and have a weekly 1:1 meeting with my manager, but also a biweekly 1:1 meeting with the skip level manager. The latter is where I am having problems. I don’t really know what to talk about in this meeting and fear that this is seen as disengagement. The first time I had the meeting, the skip level manager mentioned that he was sure I would have tons of questions and in reality I had none at all. I feel like, in my senior role, I must come into this meeting with good questions, but all questions I have, I am discussing with my peers or manager directly. So nothing left really for my skip level manager. I am starting to prepare fake questions, where I already know the answer to, just to seem engaged. It feels like a game. So please Dave & Jamison, tell me how to play that 1:1 skip level manager game.

A smiling speech bubble

Episode 433: My teammate pretends we decided, but we didn't and my team is getting worse and worse

Download

In this episode, Dave and Jamison answer these questions:

  1. Hey guys!

    I recently moved onto a new team, and my teammate has an interesting way of resolving differences of opinions. He simply says “we decided” and then follows it up with his preferred approach. These are decisions that I know have not been made.

    This engineer is mid-level, so it isn’t the “royal we” of a tech lead.

    How do I handle this? Something tells me that responding with “nuh uh!” isn’t the right strat.

  2. I’m a Principal Engineer at a large tech company who’s been with the same team for almost 8 years now! The team used to be part of a startup and we’ve been fortunate enough to be acquired by Big Tech three years ago. As a result, we’ve also more than doubled in team size. However, as we’ve aggressively grown over the last few years, I feel like we’ve inadvertently hired many “average” engineers. I find that some of our newer team members simply pick off the next ticket in the queue and do the bare minimum to progress the task. What happened to the boy scout rule? Where did the culture of ownership go? This also affects the genuinely great engineers on the team who start feeling like the others aren’t pulling their weight.

    Any advice on how to level up the culture? Or do I need to adjust my expectations and simply accept that any team of a sufficient size will have folks from a range of abilities and attitudes?