

Soft Skills Engineering
Jamison Dance and Dave Smith
It takes more than great code to be a great engineer. Soft Skills Engineering is a weekly advice podcast for software developers about the non-technical stuff that goes into being a great software developer.
Episodes
Mentioned books

Dec 22, 2017 • 38min
Episode 88: How To Dress For Interviews and Learning To Interview
This week Jamison and Dave answer these questions:
How do you dress for interviews? Full on informal beach bum? Smart casual? Formal suit tie?
I’m a new developer and have been asked to interview incoming developers. How do I learn how to interview?
This is the NoRedInk interview process. This is the blog post Jamison likes on getting data out of the technical portion of the interview. This is a slightly pessimistic look at pitfalls in the standard interview process. Google wrote a great article about structured interviewing that might also be helpful.

Dec 14, 2017 • 47min
Episode 87: Pushover Coworkers and Productivity Metrics
This week Jamison and Dave answer these questions:
My peers give up and say “have it your way” whenever we have technical discussions. How do I get them to be more vocal about their opinions?
I like the idea of measuring things, but metrics seem easy to game. How do I effectively measure team and personal productivity?
Jamison cites this tweet and this blog post about examining your own productivity.

Dec 7, 2017 • 34min
Episode 86: Sharing Salaries and Offensive Words
This week Jamison and Dave answer these questions:
Could you (Jamison and Dave) share some salary information publicly? It would help to know how much others make.
My boss uses an offensive word in technical discussions. How do I ask him to stop?

Nov 30, 2017 • 25min
Episode 85: Annoying Know-it-alls and Company Headshots
This week Jamison and Dave answer these questions:
One of my co-workers is a know-it-all, which is pretty annoying. How do I work with them?
A former employer still has my photo on their team website eight years after I left. How do I get them to take it down?

Nov 23, 2017 • 27min
Episode 84: Shy Developers and Outsourced Architecture
This week Jamison and Dave answer these questions:
I work with a very shy and anxious remote developer. How do I work effectively with them?
Our manager is outsourcing the core architecture of our next products to an offshore team. How do I tell him I think this is a bad idea?

Nov 16, 2017 • 26min
Episode 83: Gaps In The Resume and Moving To Business
This week Jamison and Dave answer these questions:
I think I’ve saved enough money to get out of the rat race. If something goes wrong and I need to get a job again, how do I explain a long gap in my resume?
I like writing code but I’m interested in moving to a more business-focused role. How can I test this without burning bridges? Do I need to take a pay cut?

Nov 9, 2017 • 36min
Episode 82: Blow Ups and Job Security
This week Jamison and Dave answer these questions:
How do I smooth things over after a blow-up between team members?
A team mate admits he writes bad code on purpose for job security. What do I do?

Nov 2, 2017 • 25min
Episode 81: Unwilling To Grow and Forced Out During Two Weeks Notice
This week Jamison and Dave answer these questions:
A developer on a team I lead doesn’t seem interested in growing. How do I help them engage more?
I gave two weeks notice, but was told part of the way through to not come in any more. I still had work left and this made me feel bad. Is this common? Did I do anything wrong?
Jamison talks about the Khan Academy engineering culture. He kinda misquoted it though. They don’t explicitly say they lay people off who don’t progress.

Oct 29, 2017 • 32min
Episode 80: New Team Leads and Constant Follow Up
This week Jamison and Dave answer these questions:
How do I keep up with new tech as a team lead?
I manage a team. A manager from a different team wants me to run everything I do in my team by him. What do I do?
Jamison mentions this by Charity Majors on the pendulum between technical and people leadership.
Jamison also mentions this HBR article on employee happiness.

Oct 19, 2017 • 38min
Episode 79: Story Point Misses and Measuring Productivity
This week Jamison and Dave answer these questions:
It seems like my teams always miss their story point commitments. Is this normal? How do you change it?
How do you actually measure developer productivity?
The article comparing research on productivity in static and dynamic type systems is here. It is a great read.
Jamison also mentions Goodhart’s Law. Read more about it here.