![Soft Skills Engineering artwork](https://is5-ssl.mzstatic.com/image/thumb/Podcasts113/v4/c5/e3/ea/c5e3ea36-a118-637a-371e-313d1a14b97f/mza_3053178667433880101.png/100x100bb.jpg)
Episode 103: Team Dynamics and Bad Code
Soft Skills Engineering
English - March 31, 2018 19:00 - 30 minutes - 28 MB - ★★★★★ - 254 ratingsTechnology Homepage Download Apple Podcasts Google Podcasts Overcast Castro Pocket Casts RSS feed
Previous Episode: Episode 102: Correcting English and Tyranny of the Urgent
Next Episode: Episode 104: Interviews With VPs and Hiring a Tester
A listener named Dan talks about ThanksBot, an internal tool at Facebook to support gratitude.
Dave and Jamison answer these questions:
I became an engineer because I loved my programming assignments and CS degree. However, at work I’m struggling to contribute beyond competing the tasks assigned to me. How do I participate more in broader technical solutions, process, etc?
I recently started a new job, and a lot of the existing code is really bad. How can I raise this concern, or make improvements to the code, without offending my teammates who wrote it? Thanks!