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 170: Code rage and code review etiquette

Download

Vote for Soft Skills Engineering on the Hackernoon Noonies awards for best Dev Podcast!

In this episode, Dave and Jamison answer these questions:

  1. How do I stop getting angry at other peoples’ code?

    Often when solving a complicated problem or implementing a feature, I have to modify or at least use systems designed by someone else. Often I find myself thinking ““Why did they do it like this??? This is so dumb!”” and literally getting mad in my chair. This happens no matter who wrote the code, and occasionally I discover that the author of the code was in fact Past Me.

    I know logically that everyone codes the best way they know at the time. So how do I avoid such a visceral reaction? Is this a common problem? Is this why many programmers seem to be Grumpy? My frustration often derails my focus and makes problems take longer to solve than they need to.

  2. What is the right etiquette for a code review for a pull request? I recently had an amazing code review. The reviewer pulled my branch, make a branch for changes he suggested and those changes all led to better and cleaner code. I felt the reviewer really tried to understand my design and test every suggestion before he wrote it. I felt that my code really got respect from the reviewer. However, a lot of my code reviews are just passive aggressive nitpicking like the comment formats are not right, the variable names aren’t clear enough. The worst was when I got a comment saying “this is already implemented” which after hours of figuring out what it meant was a different thing that would not work in my case. It seems like people have different ideas of what code reviews are and the etiquette and the expectations for it. As a reviewer and a reviewee, what should ideally happen in a code review process? Right now most code reviews are exhausting and infuriating experiences.

A smiling speech bubble

Episode 169: Conspiracy theories and flexible schedules

Download

Vote for Soft Skills Engineering on the Hackernoon Noonies awards for best Dev Podcast!

In this episode, Dave and Jamison answer these questions:

  1. One of my co-workers at the software company I currently work on has an ‘uncommon’ set of beliefs that include, among many other things, a strong mistrust of mainstream science. He is currently very concerned about the effect that Wi-Fi signals have on our health and wants the company to make some changes to our Wi-Fi hubs and our devices’ wireless connection usage. I’ve found in the past that it’s not easy to have a conversation with him about this type of topic. How can I be respectful to him and not undermine our work relationship while not giving in to connectivity inconvenience based on fringe-science beliefs?

  2. Hello! I love the show! The humor interjected into real advice (or real advice injected into humor?) makes thinking of boring and scary things like coworker relations or quitting your job sound fun! Everyone should resolve conflict and/or quit!

    I just started a new gig and I’m running into a situation I haven’t before. We have flexible work hours, but, unlike at previous jobs, people actually use them! I am meant to be pairing with another dev who is working quite different hours than me. I have a couple questions.

    1) How do we communicate about this clearly? I tried to set expectations at the onset, but it seems we missed the boat. I asked when he works, told him when I work, and it didn’t seem this far off. But on a day we’re supposed to pair, he’s here an hour and a half after me, which means I’ll leave an hour and a half before him.

    2) How do we make the time together the most effective? How can we turn about six hours of work into something meaningful, given normal distractions of meetings, bathroom breaks, etc?

A smiling speech bubble

Episode 168: Self-snooping and work from home jeopardy

Download

In this episode, Dave and Jamison answer these questions:

  1. Hey there.

    I don’t program I administrate in IT but you’re my favorite podcast, awesome job, never stop.

    I ran into a crazy situation that is WAY above my soft skills ability to deal with so I am seeking wisdom.

    I was working with someone from HR on a OneNote syncing problem. I asked someone to log in and let me look at the notebook in question that was causing an issue. I saw what I needed and then randomly clicked on another notebook so the problem notebook wasn’t open as I was trying to fix it.

    Later I approached the HR person to show me how they do something in OneNote. They opened OneNote and the page that opened up was MY employee records! OneNote syncs which page was opened last, which means the page I randomly clicked on when they were logged in on my computer was my employee record, and they knew it!

    They confronted me about it (not making too huge a deal about it). I tried to explain how I just clicked randomly and I wasn’t snooping, but it felt like everything I said only dug me deeper. I’m having trouble staying in the same room with them because of the shame (entirely internal) and I’m worried if I ever need to look at their PC again they will want full visibility to make sure I’m not snooping (not ideal). I want to make this right, but all I can come up with is honor based suicide rituals. What do I do?

    Your faithful listener,

    Stefan

  2. I’m an engineer in a small start-up. I work half of each week remotely, half in-person, as do the other engys. One of the other engineers is exceptionally skilled and experienced, way more so than I, but they are not very communicative when working remotely. The leader (understandably) becomes quite nervous as a result, especially since minor health issues have kept this engineer from working full throttle for a couple of weeks.

    What, if anything, can I do to help the leader trust this engy who doesn’t like to chatter on slack? I think they whole-heartedly deserve trust, and their work is already the backbone of this product.

    Part of the reason this matters to me is that the leader has expressed wanting to reduce work from home days to alleviate this issue. I love my wfh days, and I have been told that I communicate plenty well when working remote.

    How can I help alleviate the leader’s fears to protect another engineer’s independence and protect my precious precious remote time?