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

Subscribe Now!

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

Hosts Dave Smith and Jamison Dance answer software developers' most pressing questions about life, the universe, and everything. Join us each week to laugh at our terrible amazing jokes and gasp at our pretty good ideas pure wisdom.

Recent Episodes:

Episode 51: Junior Scrum Master In Trouble And Jamison Has No Degree

Download

Dave and Jamison answer these questions:

  1. I’m a junior developer on a team of seniors, and I’m also the Scrum Master. Our team has lots of problems. What do I do?
  2. Jamison openly talks about not finishing his degree. How did he put it on his resume or explain it to potential employers?

In question two Jamison discovers he has been lying on his LinkedIn profile for half a decade, and freaks out a little bit. The mistake is corrected, but can the damage every be undone? Tune in next week on SOFT SKILLS ENGINEERING.

Episode 50: I Didn't Quit and Manager of Zero People

Download

Dave and Jamison answer these questions:

  1. I didn’t quit my job. Did I mess up?
  2. I was hired to manage a team, but it is actually just me. What do I do?

Episode 49: Candidate Plagiarism and a Tightwad Employer

Download

Dave and Jamison answer these questions:

  1. What do I do if I suspect my co-worker plagiarized my homework assignment in their own interview?
  2. My employer is making me provide my own laptop. Is this normal?

We mention The Joel Test. Also remember to tweet about the show for endorsements from Dave and Jamison for completely serious and relevant skills like doomsday-bunker-building and yodeling.

Episode 48: Quitting a Death March & Am I Underpaid

Download

Dave and Jamison answer these questions:

  1. When and how do you quit a company that is on a death march?
  2. How do I find out if I’m underpaid?

Episode 47: Speaking Up In A New Job and Personal Issues

Download

Dave and Jamison answer these questions:

  1. How soon in to a new job is it appropriate to raise concerns?
  2. What do you do when issues in your personal life affect your work?

Thank you to Algolia for sponsoring this episode. Check out their job posting at algolia.com/softskillsengineering.

Also thanks to Battlefield: Bad Company 2, which I spent 310 hours playing.

Episode 46: My New Crappy Job and Youth vs the Status Quo

Download

Dave and Jamison answer these questions:

  1. How do I deal with my new job that turns out to be crappy?
  2. How do I know how hard to push back against more experienced engineers when suggesting a new idea?

Thank you to Algolia for sponsoring this episode. Check out their job posting at algolia.com/softskillsengineering.

Episode 45: RAPID FIRE and Micromanagers

Download

It’s our first RAPID FIRE episode, where we answer a bunch of questions rapid-ish-ly.

  1. Why do I get passed up for developer jobs?
  2. Should I take this high-paying job even though it’s a scary change?
  3. Should I quit my first job after five years?

We also answer a longer question:

How do I deal with a micromanaging project manager?

Thank you to Algolia for sponsoring this episode. Check out their job posting at algolia.com/softskillsengineering.

Episode 44: Discussing Firing and Writing Job Postings

Download

Dave and Jamison answer these questions:

  1. When I let someone go, should I tell them the reason why?
  2. How do I write a good job description?

We mention Julia Evans’ blog post A litmus test for job descriptions in the second question.

Episode 43: Internship Costs and CS Interview Questions

Download

Dave and Jamison answer these questions:

  1. What do internships cost companies?
  2. How do you feel about asking hard technical computer science questions in interviews?

The second question was prompted by this tweet:

Episode 42: Bootcamp Job Hopping and Cultural Reliability

Download

In this episode, Dave and Jamison answer these questions:

  1. Should I switch jobs to my fourth job within two years of graduating from a bootcamp?
  2. What non-technical practices and cultural attributes improve software reliability?