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
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.
CppCast
Every two weeks, or so, we sit down with guests from the C++ community to discuss the latest news and what they have been up to. Find us at cppcast.com
The Infinite Monkey Cage
Brian Cox and Robin Ince host a witty, irreverent look at the world through scientists' eyes.
Episode 216: One-on-ones and inter-team power struggles
In this episode, Dave and Jamison answer these questions: Questions I have a weekly one-on-one with my manager. What should I talk about in them? Things like feedback and career goals become old and repetitive real soon, and I end up discussing current work items. I understand that a one-on-one is my time to ask questions and don’t want it to be a longer daily-standup. My front-end team mates are in a power struggle with my back-end team mates and my design team mates. They’re intentionally making technical decisions that artificially constrain the choices of other teams. For example, design wants a certain interaction for a new feature, and my team says “nope, it can’t work that way, cause the components we built don’t allow that”. Or, they make tickets for the back-end team as in “endpoints have to work this or that way, because our components assume that structure”. This often seems detrimental and confusing to other teams. When I push back against my team they are angry. When I defend my team other people are angry. When I try to strike a compromise I feel gross because I usually think my team is wrong. I’ve tried talking with other teams and managers about the problem. I feel gross about that too because I don’t want to point fingers or throw my team mates under the bus. Where should I even start?
Episode 215: Many jobs in one and junior git stickler
In this episode, Dave and Jamison answer these questions: Questions Listener Ryan asks, I am the only full-time software engineer at a relatively small company. There is also a contractor who has been with the company off and on for about 25 years. How do I manage playing multiple roles when the development team is so small? I take the role of software engineer, team lead, software architect, product owner, project manager, designer, QA, etc. Some of those roles are full time jobs. How do I still make progress on development (i.e. coding)? Hey guys, love the show. My question is this. I work in a small startup. About a year ago our team documented what our git workflow would look like. We agreed on things like rebasing instead of merging to master, and never squashing our commits into one, that sort of thing. One of our developers is now making a fuss about following these rules and constantly does their own thing. After speaking to them about it, they shut me down and said it is up to the individual developer to decide how they use these tools. There have been some heated discussion on merge requests with this person telling our senior devs that they don’t want to hear their opinions. This person started at the company 6 months before me, and I am only a junior engineer myself so I’m not sure if there is really anything I can do. I have been at the company for 2 years now. I have offered to help them learn how to use git the way our team agreed but was told “no thanks, I’ll do it my way”. What is the best way to navigate this situation? Is this something I should escalate to my manager, or should I just get over it? Thanks for the help, can’t wait to hear you rip this one apart :P
Episode 214: Jumping ship and saying "I can't"
In this episode, Dave and Jamison answer these questions: Questions We have just today been told that we may or may not have a job in 1 week. I feel lucky because I handed my notice in yesterday for a new job, but my colleagues are not in such a position. The company burned through all it’s money, and its only hope is that someone or some company who wants to buy the business in its current state. How would you approach a situation like this? Is it best to just jump ship right away? What would potential new employers think when you told them the situation? What about my co-workers? Long time listener, first time caller asker. How do I tell my boss I can’t complete a task? I’ve been with my current company for 6 months. In that time I’ve fixed a lot of problems that have blocked our current embedded system project because of my hardware design background. Sometimes I take a bit longer than projected, but I’ve been upfront about that and it’s all fine. I was trying to implement a new feature and it was meant to take around 3 days of work to do, but after 3 weeks I just couldn’t quite get it to work. I asked for help and pulled out every trick in my arsenal and just couldn’t figure it out. I ended up having to tell my boss that I was out of ideas and letting him tell me to shelve it, but I could tell this disappointed him. What should I do next time? Show Notes https://www.youtube.com/watch?v=D4tvZJGNIhM https://en.wikipedia.org/wiki/Gnolia
Episode 213: Interviewing your future boss and screwed by private equity
In this episode, Dave and Jamison answer these questions: My manager has left, so I have the task of interviewing candidates for my future boss’ position. I’m not doing it alone, one more engineering lead joins me for my tech round. After this round, the candidate gets to talk to upper management for the final decision. My question is, what are the lines you should never ever cross in an interview when interviewing your future boss. Our company was purchased by a private equity firm this year. Layoffs began immediately. While the company was gradually carved up, leadership continually violated every promise made. This week, during the most recent round of layoffs, I lost my job. I worked my butt off for years trying to contribute as much as I could to make a positive impact for both users and coworkers. Alas, despite all of my efforts, I was proven expendable. It feels like there was little point in doing as much as I did for this company, especially during the panicked response to COVID. How do I find and sustain a sense of security at the next company? How do I ensure that I can safely care about the company—the work done and the people helping to do it—finding that precarious balance between being invaluable and burning myself out?
Episode 212: Turnover and self-inflicted complexity
In this episode, Dave and Jamison answer these questions: I’ve been working at a big software company for two years. Since joining, 10 people have left my team, which is more than 50% of my team. Usually it’s the experienced developers who leave either for a different team, a different role or a different company altogether. The latest departure of a peer who I’ve been looking up to as a brilliant developer has been affecting my mood quite strongly. On one hand, I should be glad that I’m becoming a more pivotal member of the team, having moved up in the “seniority chain”. On the other hand, I’ve always believed the saying: “If you’re the smartest person in the room, then you’re in the wrong room”. Should I be concerned about this turnover rate? Is it considered normal? Why am I feeling different about this last departure than all of the previous ones? I am the tech lead on a team at a large tech company. One of the developers on our team has consistently struggled to meet deadlines and project deliverables. He frequently seems to invent his way into impossibly complex software problems. Additionally, he also seems to lack the ability to focus on a single thread, and tries to tackle diverse kinds of work in parallel. I’ve tried to help mentor and coach him, advising him to stick to one problem at a time and try to raise his hand and has for help before he backs himself into a hermeneutically sealed NP-hard problem — but I haven’t had much success. I wanted to see if you guys had any advice. Thanks a million!!! Actual study showing actual results that we actually linked in the show notes this episode: https://radford.aon.com/insights/infographics/2017/technology/q1-2017-turnover-rates-hiring-sentiment-by-industry-at-us-technology-companies
Episode 211: Biorhythm and coworker roommate
In this episode, Dave and Jamison answer these questions: Hi there Dave and Jamison! I am a tech lead in a small team of 5 people. 4 of them start working at 10-11 AM and one of them likes to start working at 1-2 PM. This person is me. Due to my biorhythm I feel I am the most productive at this time, and I also like to do some of the non-work-related stuff in the morning. Nobody in my team has any objections but as a team lead I feel guilty because it often happens that I block someone with my work schedule. I’m trying to do as much as I can to unblock everyone - distributing tasks in the evening, making it clear everyone knows what to do - but that’s not always helpful so it usually turns out that I am stopping my morning tasks to have a call and explain something or have a text conversation. Tbh it irritates me very much :D Should I feel guilty? As a tech lead, am I responsible for working at the same time everyone does? Hey Dave and Jamison! I love the show, I’ve listened to every episode and your advice has helped me a TON! I started a new job in a different city a month ago and because of Covid-19 everyone went remote, so I didn’t physically move to that city then. Now there are talks of going back to the office, and one of the developers on my team is also looking for a place to live so we started talking about rooming together. It seemed fine to me but then I realized I’d be spending almost ALL of my time with this person who I have not even met in real life yet. Do you think this is a good idea with a lot of convenience or a recipe for disaster? Have you ever lived with a co-worker? Any advice would be great. Thanks!
Episode 210: Study time and caring less
In this episode, Dave and Jamison answer these questions: My question is regarding studying and learning new material. Before I got my job as a web developer, I was studying at least 2 hours per night, but now that I have the job (been in the job for 2 years), I want to come home and relax. How much time do you spend reading about new technology or working on new projects? Do you do it while at work or at home at your own time? I plan on getting a new job in the future and I feel I need to start studying again. I need to refresh my skills on different algorithm questions. My GitHub is empty because I haven’t worked on new projects since I got the job. Should I worry about that? How much studying should I do for future interviews? Do I need to listen to hard skill engineering podcasts to be up to date on new technology? If I’m not doing any of these already, does that mean I’m not passionate enough and I won’t do well in this career? I just had a 1:1 with a junior engineer I’m mentoring. He mentioned that he has difficulty compartmentalizing work from his personal life (for example, even when he’s not working, he can’t stop thinking about his code and edge cases and possible bugs missed). Got any life hacks to help him care less?
Episode 209: Glue and Covid ghost job
In this episode, Dave and Jamison answer these questions: Is a “glue person” valuable on a software team? Someone who isn’t the strongest developer but is liked by teammates and builds a cohesive team dynamic. A while ago I interviewed with a big company. Right after completing a code challenge, covid-19 got out of hand in my country and they sent me an email saying they are putting the process on hold. Weeks have passed and I came across a job opportunity posted recently by the company for the position I was applying to. I felt betrayed. I emailed the recruiter asking for follow-up and she said that they are sorry about the situation and that they wanted to schedule a meeting. The question is, should I let them know I was displeased by this or is this really a non-issue? Do I risk my chances by doing so? Am I acting like a jealous teenager? Thanks a lot and love the podcast, stay safe!!
Episode 208: Toe-stepper-on-er and high leverage work
In this episode, Dave and Jamison answer these questions: Hi Dave and Jamison, my name is Bob Marley. I am a senior software engineer at a tech company. How do I deal with a chronic toe-stepper-onner? I have a coworker named Jimi Hendrix - also a senior software engineer - who has a habit of getting involved in and trying to manage my projects. He joins meetings and slack channels, uninvited, and starts asking people for status updates and questions them why things are done a certain way (and not the other), what’s taking so long on unfinished tasks, etc. Jimi basically feels that my projects are his to oversee and manage. So far, my response has only been passive aggressive - e.g. taking discussions to a different slack channel or thread, or meeting the team members offline when he is not around. This is obviously not working out and it is not sustainable so I’m looking for some advice on how to deal with it. It’s not hindering the project so I don’t have a strong reason to complain. Other than the fact that it drives me nuts when Jimi gets involved and asks for a status update on a project which I have fully under control. Should I just do nothing and wait for the problem to go away due to him getting moved to a different project? But how do I keep my sanity until then? And what if even then he finds a way to step on my toes? Have you guys experienced this kind of situation? Is there a permanent solution to it? And no, I don’t want to quit my job. Please help! Yours truly, Bob Marley Hi Dave and Jamison. Love the show. I have been gathering informal peer feedback from my team. I was told I am doing well, and I should be doing “more high leverage work”. I interpret that as coming up with design patterns, best practices, and mentoring other developers. I mentioned that to my manager, and while he agrees, he also said there is no additional head count for the coming year, and knowing that there is a backlog full of features, my concern is that I will be the primary person tasked with writing those features. How could I negotiate/convince my manager to let me do more tech lead work instead?
Episode 207: Unclear career goals and garbage code
In this episode, Dave and Jamison answer these questions: I’m a senior software engineer at a fast growing software startup. In the past year and a half that I’ve been with the company I’ve gone through 5 reorgs and have had 5 different managers in 4 different teams. Each time I sit down to do a 1 on 1 with a new manager they ask about my career goals and aspirations. Initially, when I joined the company I was a weak and feeble non-senior software engineer. When I was asked this question then, my answer was “to learn and grow, and have more authority and autonomy over the systems that I build, and be considered a senior software engineer”. Over the past year and half I have proven my worth and paid my dues and got the title of senior software engineer, along with the pay raise that came with it. My career development horizon has not been very broad. I didn’t even know there were levels beyond senior software engineer for a long time. I feel like I’m missing out on growth opportunities by not having a clear answer to this question. Please help! Love your show, keep it up. I career switched via a coding bootcamp 3 years ago and have been at my current company ever since. The bugs created by my garbage code from the early days made me a big believer in clean code practices — I now feel strongly about using descriptive variable names, avoiding duplicate code, etc. However, my boss/CTO is on the opposite end of the spectrum. As long as the code works, he doesn’t care what it look like. I want to stay at this company because I strongly believe in the product and I love the flexibility of a small start-up, but my boss and I keep bumping heads. For example, we recently switched over to PRs, and each PR my boss has made included blatant violations of the coding standards document we created together (!). When I request changes on the PR, he says he’ll do it but it isn’t a good use of our time to rewrite it when the code works. My question is two-fold: (1) As the most senior engineer on the software team, how can I go about promoting a quality-driven approach when the CTO doesn’t see the value in it? (2) If all else fails, I’m open to quitting, but I don’t want to end up the same boat. During interviews, what questions can I ask to find out if the company truly values code quality?
Episode 206: Micromanaging WFH and vaguely tech lead
In this episode, Dave and Jamison answer these questions: Due to corona virus, we had to work from home. But the manager, is checking up on us very frequently. We have to give the day’s plan at 10:00am sharp, otherwise he assumes that we are taking the day off. Also, we have to send an email listing the things we did at the end of the day. This is on top of using jira. I feel he is micromanaging a lot and because of this, the team isn’t able to work efficiently. P.S. Now he wants us to add our tasks to a Google sheet. Hi Dave + Jamison, First of all, thank you for putting on the show every week. It is definitely my favorite podcast by a wide margin, every Monday I just keep hitting refresh waiting to get my weekly fix. I started my job about 10 months ago in a late stage startup. In my last annually review, I was recognized for all my hard work and was made into a “Tech Lead”. I am not sure what this means. There is no “tech lead” title in the company wiki. Everyone title is just “software engineer” with a level. The salary adjustment definitely suggest this is not a promotion, and the all important company wiki says I need to wait to get promoted anyway. What is your advice? What should I start doing now, what does it mean for my career?
Episode 205: Old code outage and questions leaking
In this episode, Dave and Jamison answer these questions: Ever since I graduated from college, I’ve been working in a rising tech company for almost 5 years. I’ve been working on some project and different teams, and it has been more than 1 year on my current team. One day, someone mentioned me that their service is down because of my code from when I was on the previous team and I didn’t even touch that code for almost 2 years. I explained that I am in different team now, so I refer them to the current members of my old team. I also gave some suggestion on how to fix it, but that team didn’t respond fast enough and eventually other person fixed it. Somehow I feel really guilty that I didn’t do anything to fix it. My question is: Until when I responsible for the code I wrote? Is it as long as I’m on the team, or as long as I’m still working in the company? Please advise. Thank you. An external recruiter learned what would be on my technical screen from a previous candidate and shared that with me. Should I warn company X that their technical screen is compromised?
Episode 204: Remote work and ghosting your employer
In this episode, Dave and Jamison answer these questions: My whole team recently transitioned to working from home. How do I handle this? The good news is I don’t have a fever. Working remotely, what should you do if either you ghost the company or the company ghosts you? (Ghosting as in the relationship)
Episode 203: Downturns and conflict
In this episode, Dave and Jamison answer these questions: I am worried it is only a matter of time before the growing pandemic impacts the job market. I work for a young start up, and as of yet I am gainfully employed. But if this goes on as long as some folks say it will, I’m just not sure. I’ve heard there was a software job market crash after the dot com boom. What was that like ? What’s the best thing to do if you get laid off in a market downturn? Wait it out? Look for software jobs? Switch industries, temporarily? I’m a technical lead on a small team. Two of my teammates are constantly annoyed with each other and I need to know how to talk them down so we can be a better team. Let me introduce them: Alice (the names are made up), an experienced programmer, who is slower to catch on, keeps dragging old arguments and old ways of thinking in, works very slowly and in her own vacuum, and often comes across as difficult to work with. Alice constantly disagrees with the team on things like naming conventions and solutions to problems. In the other corner, Bob, a 2nd year coder, eager to follow leadership but still learning when to ask for help. He takes criticism constructively, but not from Alice because to him it sounds like fingernails on a chalkboard. Alice and Bob constantly bump heads. Yesterday, Bob rewrote Alice’s stored procedure because it was slow and he had some ideas with how to reuse some code. Today it was SQL formatting - Bob’s SQL is ugly, according to Alice, who wants to confront him on it. I suggested we create a style guide to settle that argument. This kind of thing has been going on since the team was formed. My question is, what can I do? They both look to me as the leader, and I don’t want to take sides, but we’ve had this problem for nearly two years.
Episode 202: Can't stand up and new team, new me
In this episode, Dave and Jamison answer these questions: Hey Dave and Jamison. Due to a chronic joint problem, I find it uncomfortable to stand for more than a couple of minutes. How do I talk to my boss about sitting during standup meetings? If I change workplaces, when do I talk about it to a new boss? I look and walk just fine, so people usually don’t realize that there is something wrong with me. I’ve already been to the doctors, and there is not much they can do, so I need to soft skill engineer my workplaces. Hello! I love your show! I am an entry level engineer that had graduated college with a B.S. in Computer Science in May of last year. I was on my previous team for about six months doing mostly documentation and asked for more development work because I didn’t have a lot of experience in hardcore dev work in my past internships. My manager, some of my team members, and the lead systems engineer gave me high props that helped me get onto a new team. I’ve been on the new team for two months but I am having a hard time finishing my tasks. I try to do things on my own before I ask for help, but it seems that I’m always stuck or can’t get the code to work in a reasonable time. My team has a strict deadline at the end of March. I have multiple tickets in Jira assigned to me before then. When I ask for help, it seems like my team members just finish my tickets for me. I feel like a fraud and it really doesn’t seem like I am delivering. People had praised me for my work to get on this new team, I don’t have anything to show for that praise. How did I even graduate from college with a Computer Science degree? Do you have any advice on my situation?