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 134: Boredom vs Money and Agile vs Long-Term Schedules

Download

This episode is sponsored by Pluralsight. Pluralsight is hiring data scientists, machine learning engineers, and software engineers. Check out the jobs at https://pluralsight.com/softskills

In this episode, Dave and Jamison answer these questions:

  1. I’m current doing nearly nothing at work (not by choice) and getting paid a king’s ransom for it, just to stay on the roster. I’ve never been in this situation before. Would I be foolish to give it all up just to not be miserably bored? I’m pretty sure this isn’t sustainable, and I’d get laid off in the next economic downturn before you guys might get to my question, but just curious what your insights are.

  2. How to deal with teams that are run as “Agile”, but management who want timelines and deadlines to steer the business?

    I’m at my second large software development company that’s following the agile/scrum ceremonies with weekly sprints that entail grooming/planning/retro meetings. Management keeps track of progress to align the efforts of multiple teams spread across the organization. I’ve noticed over the past year an increased desire for estimated timelines for when each team will be done with their portion of the project. This forces the team to groom and size stories months out ahead. These estimates end up becoming deadlines that need justification to be pushed back, which is common since as you get into the work you find more stories need to be added.

    I had a very similar experience at my last company. Both have 5-10k employees.

    I understand the needs of the business to plan ahead. So saying “it’ll be ready when it’s done” is not a good answer. However, it feels like we’re constantly falling behind arbitrary deadlines and in a constant frenzy to catch up.

    So….what do?

A smiling speech bubble

Episode 133: Herding Linter Cats and Surviving Until Severance Time

Download

In this episode, Dave and Jamison answer these questions:

  1. How can I make my team be more proactive and go out of their comfort zone more?

    I recently started a new job as the team lead for a team of four developers. Each developer has their own pet things that they keep themselves busy with; one likes to configure linters, another has a long-running project they keeps to themselves, and so on.

    We have been tasked with a new, high-priority project which involves new technology and would require everyone to pitch in. So far, though, that has only happened when I’ve directly asked someone to do something.

    I absolutely do not want to end up in a position where I have to tell people what to do. How can I make them realize that this new thing should be their top priority, even if that means going out of their comfort zone?

  2. TLDR: My role and product are moving to a different country. I don’t want to relocate.

    I have to stick around at least another 3-4 months to get my redundancy package. In some ways this is great as I’m pretty unprepared for interviewing right now. On the other hand, this is terrible because I’m pretty unprepared for interviewing right now.

    How do I keep morale up, for me personally and the wider team during this period?

A smiling speech bubble

Episode 132: Should I tell my boss I'm planning to quit and keeping tech talks going

Download

In this episode, Dave and Jamison answer these questions:

  1. Recently I was approached by a manager and informed that I needed to decide if I wanted to stay at the company or not. I initially said I would like to stay, and was told there was some negative feedback from coworkers I’d need to work on to do so. I agree that these were issues I need to work on to become a better engineer, so I’ve engaged in something like a performance plan with her over the last few weeks. But I’ve decided that I don’t want to stay after all, and I’ve started sending out applications.

    I don’t want to burn bridges when I do end up putting in notice, but I also would like to continue working with her on these issues, and I’m worried if I declare I am leaving that will end. So my question is: should I tell my manager I’ve changed my mind, or stay quiet?

  2. We used to have regular “tech talks” in the office - opportunities for people to share something they find interesting that doesn’t have to be work related but usually is tech/development focused.

    The talks were 30-45 minutes in length, and there used to be free food (at a place that doesn’t normally do that kind of thing)

    I wasn’t here at the time when it last fizzled out, but used to give similar talks at my last company and I’m interested in starting them up again here. People say they’re interested now but the novelty of free food eventually wears off - do you have any suggestions as to how to sustain people’s interest in attending giving talks?

    I might be able to convince a few people I work more closely with but there’s 60+ or so technical people in this office I’m still getting to know.