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
Thinking Elixir Podcast
The Thinking Elixir podcast is a weekly show where we talk about the Elixir programming language and the community around it. We cover news and interview guests to learn more about projects and developments in the community.
Accidental Tech Podcast
Three nerds discussing tech, Apple, programming, and loosely related matters.
The Infinite Monkey Cage
Brian Cox and Robin Ince host a witty, irreverent look at the world through scientists' eyes.
Episode 155: What do you think about employee monitoring software and how do I get un-demotivated after losing interest in software dev?
This episode is sponsored by the O’Reilly Velocity conference. Register today and use discount code SKILLS for a 20% discount: http://velocityconf.com/skills. In this episode, Dave and Jamison answer these questions: Hello! Thank you for the show! What do you think about employee monitoring software? I received a message from a company about a job position and they use such software. It seems weird for me to make screenshots on my computer and to see what software I’ve use and what websites I’ve open. How do you feel about it? I’m a software engineer with about 2 years of professional experience. When I started working, I was motivated to learn all the things. I consumed technical blogs and podcasts in my personal time and proactively identified and solved problems for the team. Things recently changed. I can’t bring myself to care about work anymore. Curiosity used to come naturally to me but I can no longer summon curiosity about anything related to software development. A few things lead to this. 1) I got a lower than expected rating on my performance review due to an issue with my soft skills. I thought the feedback was valuable but didn’t think such a rating was warranted, considering my overall contributions. 2) Our team has spent the past few months writing code that didn’t ship. 3) I took the Soft Skills Engineering advice and got a new job. In order to do that, I spent many mornings and weekends preparing for technical interviews. After accepting the offer, I felt totally burned out. I very much want to be back to my previous, curious self by the time I start my new job. Unfortunately, I can’t take a long break before the start date. How can I get to a place where I feel motivated again?
Episode 154: Why am I terrible at picking candidates and how soon can I quit my job?
This episode is sponsored by the O’Reilly Velocity conference. Register today and use discount code SKILLS for a 20% discount: http://velocityconf.com/skills. In this episode, Dave and Jamison answer these questions: I keep getting asked to interview new candidates. But my interview feedback history is pretty bad. I’ve said yes to hiring: Someone who’s super smart, but drives me absolutely crazy with constant argument and may cause me to take the time-honored Soft Skills advice and quit my job. My boss at my former company, who DID drive me to quit my job. My first (and only) hire back when I was a people manager, who turned out to be terrible, but I was told I had to keep him around because “it would look bad” to fire my first hire. What should I do? Is it acceptable to just keep turning down interview requests? I’ve wandered into a tech lead position, so I suspect I can’t dodge them forever. But I don’t want to keep suggesting bad hires just for the sake of getting more interview practice. Thanks for all the advice and the laughs! I’ve been a regular listener for a couple years. How long do I need to wait before bailing on a new job I don’t like? More than a month? It’s not totally miserable: the people are nice and the company has good prospects. But the technical decisions of the team lead to daily frustrations for me.
Episode 153: Informal Leadership and Dealing With Burnout (rerun of episode 71)
This episode is a rerun of episode 71 from August 2017. In this episode, Dave and Jamison answer these questions: I’m sometimes an informal lead on project teams. How do I help the team get stuff done as a peer? How do I deal with burnout after an extended period of crunch time? Jamison mentions the blog post by Jamis Buck called To Smile Again where he talks about his experiences with burnout.
Episode 152: How to pair program as an introvert and being mistreated as a contractor?
In this episode, Dave and Jamison answer these questions: Hi guys! Big fan of the show. Here’s a question: What to do if I hate working in pairs? I’m in a tricky situation. I work on a great project in a team of great people We try to implement all the good programming practices. Retrospectives, cross-review, working in pairs.. I hate working in pairs. I am a typical introvert-programmer and the thing I like the most about programming is that you can sit all day digging around the code and NOT communicate with the people. Or at least not all day. But how can I say that to my teammates? “Hey, I would rather work alone than talk to you guys.. By the way, love y’all!” It seems impossible to communicate that to my co-workers without hurting them. And moreover, this is a good practice. Which makes me feel horrible because I feel super-tired after whole day of talking to people. Plus I also feel like somehow I take up their worst qualities: if the person is slower, I become slow too, or start making mistakes. Help!! Hey guys, big fan of the show here. Thanks for your advice and time. The company that I work for provides “tech teams” for hire. In other words, American companies that want to outsource part or all of their tech team to a cheaper location can hire us and get developers and PMs at a fraction of what it costs in the US. I ended up working with an established fitness company based in NY. Their management insists that we are “regular” engineers in their tech team and we should participate in their technical discussions, agile meetings and so on. However, their engineers seem to be on a completely different page and treat us like monkeys that can write some code. For the most part, I can deal with their condescending treatment and everything else they might throw my way. The problem is that the company is currently in a very intense project and they are all “stressed” which seem to provide them license to be extra rude BUT ONLY TO CONTRACTORS. Their managers brush everything under the excuse of stress but I’m sure that wouldn’t fly if we were “regular” team members. How would you handle this situation? Any advice before I lose my temper? I’m also afraid that getting rid of a contractor is much much easier than firing an actual employee.
Episode 151: Where are all the old developers and Do I not ask enough questions?
In this episode, Dave and Jamison answer these questions: I have a lot of software developer colleagues who are 20 - 35 years old but none 50+. At what age does a software engineer’s career end? Hi Dave and Jamison, thanks for the great podcast. I recently started a new position on a small remote team. The co-founders are increasingly dismayed by my lack of Slack-question-asking, although I have reassured them that I’m not too shy and I will ask when I’m stuck. I have daily one-on-one meetings with one co-founder, where I do ask questions about the code base, story requirements, potential side effects of my solutions etc. It’s an open-source project with comprehensive and Googable developer docs, so between those and my debugger I can figure everything else out with a bit of research. A co-founder told me that he expects to see me asking one or two questions per hour, and strongly implied that I need to do this if I want to survive my probation period. I was actually let go from my last job at the end of my probation period due to “brisk communication style” and “not asking enough questions”, so I’m freaking out now. I don’t want to annoy my colleagues with a constant stream of inane RTFM-style questions, but I’m stumped on how else to hit my question target! Can you help me come up with ideas? Is there some big picture reason for this obsession with question-asking that I’m missing?
Episode 150: How to fight imposter syndrome as a technical lead and Getting in to meetups
In this episode, Dave and Jamison answer these questions: I worked for four years doing web development for a company while I got my degree, and loved it. I eventually became the lead developer because I had been on the team the longest. I thought it was really cool. I worked with the team to make organizational tech decisions, trained new hires, held regular meetings to discuss projects. After about 6 months, though, imposter syndrome started sneaking in and I felt like I was making things worse, not better. I figured the team needed someone who actually had senior level experience, and the pressure was getting to me. So I bailed. I’ve since had a few people approach me and say they want me to join their early-stage startup in a technical leadership position. I haven’t outright declined, but I’m nervous about being put in a position where the stakes are even higher. My question is if the pressure of being responsible for everything ever lessens. Is it something that gets better as you get more experience? Is everyone in technical leadership feeling this pressure and doing a good job to hide it? What can I do to gain the confidence to eventually lead another team? How do you step into the meetup scene? I have not attended one before, but the idea of them is interesting. However, there is this feeling that I would not fit in due to inexperience.
Episode 149: How to get my engineering career back on track and how to thrive in a heavy process environment
Joining us this episode is special guest Nedda Amini! In this episode, Nedda, Dave, and Jamison answer these questions: My engineering career started out pretty promising. But along the way, I took a couple of unfortunate decisions and jobs, that instead of helping me grow as an engineer, were a big setback. When you career takes a few too many bad turns, how do you steer it back to where you want it to go? I work on product development with ~25 other developers, and management recently had us all embark on a journey to gain some level of CMMI appraisal. The goal is to deliver higher quality software at a more predictable pace. In practice this means that we got more processes to follow, more meetings to attend and more time-tracking fuss. I’m trying to keep an open mind because I, as a programmer, also have high standards for the product and it’s development. I’m scared that programmers are being turned in to factory workers stripped of any autonomy. These new processes don’t allow me to do anything without my product owner’s approval. I’m afraid that it will limit my creativity and ultimately cause my work and the product to suffer. In this kind of scenario, what’s your advice for a programmer who often gets inspired to remove tech debt, tinker with our dev environment, and otherwise make small improvements and refactorings that shouldn’t require management approval? What’s your opinion on the level of freedom that programmers should be provided in order to do their job well?
Episode 148: In the orbit of a Rock Star Programmer and Should I share my salary with my coworkers?
In this episode, Dave and Jamison answer these questions: I’ve been an engineer for about 5 years and in the last two jobs, rock-star programmers have made my life very difficult. I define rock star programmers as ones with ability to produce lots of code and implement features at a pace that dwarfs my own. In my last job, the RSP would constantly rewrite core libraries and I would have to figure out his design and rewrite my code to adapt to the new design multiple times. In the current job, the RSP is very uncommunicative but with his sheer productivity steers the project into wild directions that are always coming as a surprise. Half the time my work then becomes throw-away because I was working based on the previous design. Am I a slowpoke and I’m seeing a normal programmer as a rock star or are these programmers just slightly above normal programmers but creating lots of work for everyone else? Managers are completely starry eyed at RSP and so talking to managers seems like a bad idea. What should I do? How do you feel about sharing salaries amongst your co-workers? I’m about to have my yearly review and I get the sense that my raise (which has already been promised to me) will be underwhelming given how stingy the company has been previously. That is simply a hunch based on previous experience and the fact that our team budgets have tightened up in the past 6 months. Recently a co-worker let it slip what his salary is, and though I don’t like playing the comparison game, it made me feel underappreciated. I discovered that he was making the same salary I was, but for lower quality of work and less contributions to the team. I’ve heard some devs in other companies advocate for sharing salaries amongst their peers, but I’m not sure if it’s a good idea. Will sharing my salary and encouraging my co-workers to do the same, allow for myself and my co-workers to better understand our value and help us negotiate raises? Or will it simply foster resentment and division?
Episode 147: How to grow in a flat organization and how to get references when job hunting in stealth mode?
In this episode, Dave and Jamison answer these questions: I work in a flat organization. There aren’t really any titles, and very few managers. There is no common “climbing the ladder” here. What are options for career growth that will help me feel confident that I am progressing in my career? How do references work? I’m starting to look for a new job which means potential employers are going to be asking me for references. I’m not ready to let my boss know I’m thinking of leaving and aside from my current coworkers I don’t know who would attest to my ability as an engineer. I work for a small company (under 50) in an even smaller firmware department (about half a dozen). What am I to do?
Episode 146: What to do with sick co-workers who come into the office and dealing with weird performance review feedback
In this episode, Dave and Jamison answer these questions: Hi guys! I was faced with quite a dilemma recently. A few days ago one of my co-workers said he was sick and worked from home. But the next day he came to office, constantly sneezing and looking terrible, and for some reason finished the day in the office. The same happened the day after that. I didn’t want to be rude and I felt for this guy, but I didn’t want to get sick either cause I have some important tasks this week. What could have I done? I could not just tell him “go home you fool, you’re contagious!” I could say “Hey! I noticed you’re not feeling very well, why don’t you come to the manager and ask to work from home this week?” But I didn’t have the guts to do this. Besides, what if he couldn’t work from home for some reason? I solved this by lying to my manager that I’m ill too, and worked from home. What is the best solution here? Hi, I recently went through my company’s annual review process. The review went pretty much as expected, with things that I was doing well and things that I could improve on. However, I received some negative feedback which I disagreed with. I asked for additional detail and examples of this, but neither my manager, or his manager (our site lead) could give me any concrete examples. After some further discussion they agreed to remove the comment from my review, but I’m now left wondering why this feedback was added in the first place if there were no examples they could give me. Their explanation for this was that it was feedback for our team, am I wrong or is an annual performance review the wrong place for that kind of feedback? Should I be concerned that they actually do have feedback for me, but were unwilling to do so given my reaction? Is this enough of a red flag to maybe consider looking for a new job?
Episode 145: What to do with a bad manager who is loved by upper management and should I include detecting major security vulnerabilities on my resume?
In this episode, Dave and Jamison answer these questions: How do I deal with the manager on my team who is both not very technical and positions himself as the “boss” spending almost no time with the team (except dragging everyone into more and more meetings! 😡) . My manager upsets and demotivates the team but not upper management and is clearly trying to climb the career ladders as fast as possible. Obviously everyone wants the team to succeed but the friction is growing. Some team members already left with (maybe too subtle) hints at the problem. Should one stage a coup and take over? Silently manipulate people to go to into “the right” direction? Switch teams/jobs and see it burn from the sidelines 🍿? While testing my system at work, I was shocked how little security there was. Two issues exposed the entire system’s data by just changing the query string. Also every API call had no backend check on the user making the call. These are just two examples of many. This is at a gigantic multi billion dollar institution handling hundreds of thousands of people’s data, some of it incredibly sensitive. This fact will be known on my resume. This leads to my question: I am looking for a new job now, and wondering how much detail about these security issues is appropriate to share on a resume? I feel this helps me stand out as a newer dev, but would this be frowned upon by prospective employers that may worry I might overshare their own security issues? Thanks for all your help!
Episode 144: Job hunting while employed and how to start my first technical lead role
In this episode, Dave and Jamison answer these questions along with special guest Jonathan Cutrell:: I’ve been job hunting while employed (gasp), and I have a number of opportunities that have advanced to the in-person interview. Most of the requests I’ve seen have said that they’ll be 4-5 hours in the office (which seems fairly typical). The problem is that I don’t have unlimited vacation, and I feel dishonest taking so many days off. How can I navigate new opportunities without disrespecting them, or completely failing in my current responsibilities? Hey guys, great show (though I think, as with all shows, it could probably use more discussion of badgers [yes, I said badgers!]). I’m about to start a new job (I took the time-honored and hallowed show advice, though I’m leaving on great terms with my old job) and will be coming in as that fanciest of newly-invented titles in software, Staff Software Engineer. This is the only third time I’ve started a new job [not counting odd jobs in high school and college], and I’ve never stepped into a leadership role before when starting. What are the most helpful things you’ve done or seen other engineers do when joining a team in a technical leadership role? Thanks! Follow Jonathan Cutrell on Twitter @jcutrell and subscribe to the Developer Tea podcast: https://spec.fm/podcasts/developer-tea.
Episode 143: Dealing with meeting interrupters and setting work limits
In this episode, Dave and Jamison answer these questions: I have noticed one of my coworkers, a fellow senior software engineer, often interrupts people during their meetings with his comments and thoughts. While I’m not against voicing opinions during a meeting, he does it so often that he takes over meetings. Some of his points are off-topic. He’ll cut off the presenter or another colleague (who displayed good etiquette) mid-sentence, not letting them finish their thought and derailing the flow of the meeting. In our last meeting I tried to quickly respond to his interjections rather than let him finish so we can keep the meeting moving. I thought he would take the hint to think a little more before interrupting. Ineffective so far. I think next time I will recommend that all questions and concerns be held to the end so we can get through all the meaningful content before letting him speak. Any other suggestions on how to deal with people like this? Hi guys! I have a question about setting limits to your work. I hear that its a common practice among developers to set restrictions to their work like turning off slack notifications when at home, not staying late at work, etc. This seems like a healthy approach, and I like it. But I can’t bring myself to do it. I’m a successful developer, I love my job, and I love the work communication in our chat. I have no problems struggling through the workday, but I have problems not falling into work in my free time. I have a lot of friends, a lot of hobbies, I’m definitely not bored outside of work. But still I always have this inner desire to open and read the workchat when I have a free minute, or finish an interesting feature in the evening instead of reading an interesting book. I can’t say it makes me unhappy in some way or affects my private life - I still will go and see a friend if I’m invited and still will attend my yoga class on a normal schedule - but this ““desire”” distracts me sometimes and that’s not normal either. Am I right?
Episode 142: Can I get hired above my level even though I look inexperienced on paper and should I be brutally honest in peer performance reviews
In this episode, Dave and Jamison answer these questions: On Episode 66 you attempted to answer my question: ‘How bad can a Junior Front End Developer be?’ Well, I’m now 4 months into my new job as a Junior Front End Developer and it turns out, they can be pretty bad! I’m in this junior role I feel overqualified for. My peers rate me as a solid mid-level, and I’ve started to realize that I’m not really a “junior”. I think this can all be attributed to learning from really good devs at my last company. My best friend is a Senior JS Contractor (legend) and I talk to him about code and best practices everyday. Question: Would you ever hire someone at a mid-level role even if they only had 6 months of profressional experience? i.e. how much weight do you put on the CV? I love you guys, listened to every podcast! Thank you so much for the show, I’ve been binge listening to old episodes ever since a friend of mine suggested it. Your excellent, and often comedic, advice has been getting me through the work day and I really appreciate it! Onward to the question! One of the members on my team, who is more senior than me, often does poor work, and the rest of the team picks up the slack to redo the work, pushing out deadlines we would have otherwise met. I know better than to vent about this at work even though it is very frustrating, however now I’m in a bit of a predicament. Part of our annual review process requires us to provide feedback on each of the members of our team which is not anonymous. The feedback is used to make decisions about raises and promotions. This individual has mentioned that they expect a promotion to a team lead position in this upcoming review cycle, which makes me quite nervous. Should I be honest in my review and mention my concerns or should I take the much more comfortable route that will also protect relationships on my team of pretending everything is fine.
Episode 141: A Rampant Rewriter and Dealing with an Overexplainer (rerun of episode 73)
This is a re-broadcast of episode 73 from August 2017. We’ll be back next week with a new episode! In this episode, Dave and Jamison answer these questions: A developer on my team has been rewriting my code under the guise of “code cleanup” without saying anything to me. Is this normal? What should I do? How do you deal with co-workers who over-explain unimportant issues?