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.
Similar Podcasts
The Infinite Monkey Cage
Brian Cox and Robin Ince host a witty, irreverent look at the world through scientists' eyes.
24H24L
Evento en línea, de 24 horas de duración que consiste en la emisión de 24 audios de diversas temáticas sobre GNU/Linux. Estos son los audios del evento en formato podcast.
In Machines We Trust
A podcast about the automation of everything. Host Jennifer Strong and the team at MIT Technology Review look at what it means to entrust artificial intelligence with our most sensitive decisions.
Episode 40: Office Visibility and New Tech
In this episode, Dave and Jamison answer these questions: How can I encourage my team to be more visible in the office? How do I learn new technologies without going through a noob phase?
Episode 39: Brilliant Jerks and One on Ones
In this episode, Dave and Jamison answer these questions: How do I deal with engineers who are skilled technically but rude and demeaning? What should I talk about in one on ones with my manager or reports? We also cite Questions for our first 1:1, a blog post by Lara Hogan.
Episode 38: Going Over Heads and Firing Just After Hiring
In this episode, Dave and Jamison answer these questions: When is it appropriate to go over someone’s head? Should I fire the new engineer that we just hired (and who relocated to take the job)?
Episode 37: VC Funding and Internal Presentations
In this episode, Dave and Jamison answer these questions: How does venture capital work, and how does it affect me? How do I give great presentations at work?
Episode 36: Unlimited Vacation and Enforcing Best Practices
In this episode, Dave and Jamison answer these questions: What do you think of unlimited vacation policies? How do I enforce coding best practices? Show notes, because Jamison is feeling ambitious: The Netflix culture slides we mentioned pylint, the linter Dave talked about
Episode 35: Attracting Talent and Quitting Responsibly
In this episode, Dave and Jamison answer these questions: How can I attract talent? How do I quit without burning bridges?
Episode 34: Do Certifications Help and How Can I Avoid Avoidance?
In this episode, Dave and Jamison answer these questions: Do certifications help me? How can I solve an avoidance problem?
Episode 33: Damaging Your Credibility and Meeting Potential Employers In School
In this episode, Dave and Jamison answer these questions: How can a developer damage their credibility online? How can I meet potential employers while I’m still in school?
Episode 32: Why Would You Do Contracting?
In this episode, Dave and Jamison answer this question: Why would a developer leave a full time job to do consulting or contracting? It just so happens that Jamison did this a few months ago, and he shares his experience in making the transition.
Episode 31: Going In To Management and Knowing If A Job Is Worth Applying To
In this episode, Dave and Jamison answer these questions: Should I go in to management? How do you know if a job is worth applying to?
Episode 30: Reaching Consensus and Code Editing Etiquette
In this episode, Dave and Jamison answer these questions: How should you reach consensus on a team? Should you always have consensus? What is the etiquette around editing code in a shared repository?
Episode 29: What Should I Do When Starting A New Job?
Literally the only episode that the advice “quit your job and get a better one” doesn’t apply. Dave and Jamison answer the question: What should I do when starting a new job?
Episode 28: How Long Should I Stay At My Job and How Do I Help Junior Developers Improve
In episode 28, Jamison and Dave answer these questions: How long should I stay before I quit my job? Two to three years seems fairly normal. Dave sees people with less than 12 months regularly. Staying at a job means you experience things you wouldn’t if you hopped around a lot. It is much easier to see the hype cycle play out if you stick around. You get to see the outcome of your own decisions. Quitting usually == raise. Chronic job hopping might result in a reputation of not sticking with things. Dave thinks you should quit your first job after 18 months because of the Monty Hall problem How do you encourage junior developers to improve? We assume that these junior developers really want to improve. Make it clear that people get stuck and struggle, and that is normal. Make it clear that you don’t want them to get too stuck. Make it OK to ask questions. People generally live up or down to your expectations, so help them feel trusted and that you expect they will be great. Make the outcome of their work clear.
Episode 27: Writing Great Resumes and Pushing Back on Non-Engineering Tasks
In episode 27, Jamison and Dave answer these questions: How do I write a great resume? Do you really need a resume these days? How important is formatting and good design? What content should be on your resume? Should I push back on non-engineering tasks like PowerPoint presentations? From listener samspot: I am a Sr. Developer and I am often asked to spend time on PowerPoint presentations for funding and other business stuff. I want to ask why the managers, analysts, etc can’t handle these tasks. I find them to be a frequent distraction from my actual responsibilities, especially because these are so frequently “emergency” requests. Should I push back on this work, or is it better to be a team player?
Episode 26: Communicate Your Efforts and I Told You So
In episode 26, Jamison and Dave answer these question: How do you make sure people know about your good work? See Matt Zabriskie’s great post for background on this. We also mentioned Do Things, Write About It. How do you get your point across effectively so you don’t have to say “I told you so” later?