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.
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
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.
Episode 349: Performance review dissonance and being a remote manager
In this episode, Dave and Jamison answer these questions: I am a senior engineer looking to make staff. Every week at my one on one I ask my manager what I can do to improve and always receive the answer “keep doing what you are doing”, but when I receive my performance review, I don’t receive top grade or promotion and there are listed areas of improvement. How should I feel about this and what should I do? I’m a software group manager for a medium sized applied research organization that deals with both software and integration onto hardware. I am fully remote while the rest of the company has returned to the office due to the integration work with hardware. I started managing just before the pandemic. What are some effective strategies to deal with this setup? What are some typical gaps or issues to look out for? How can I reassure team members that may be skeptical of this setup, as well as peers and my bosses? I do have full support from above as of now. My rough thoughts so far include: be candid about limitations of this setup, experiment and iterate quickly on communication and collaboration processes, solicit regular feedback, and use it as an opportunity to grow members of my team into seniors and tech leads by having them focus on mentoring juniors and managing integration with other teams.
Episode 348: Making too many mistakes and low code career risk
In this episode, Dave and Jamison answer these questions: Hey Dave and Jamison, long time listener of the show. looking to get your advice on dealing with guilt at work. Lately, I’ve found myself in a lot of situations of having to deal with bugs/incompleteness after pushing out a feature. It’s not my intention to be careless and I do feel like I’m giving it my 100% but there seems to keep being thing after thing that I’m not catching. It’s impossible to sweep these things under the rug when you have to put up a follow-up pull request to fix something that was clearly your fault. I feel like every once in a while is okay but when it starts to become a pattern, I wonder how this may reflect on my performance review. My coworkers aren’t letting on about any frustrations they may have but every time this happens, I can’t help but feel shameful of myself and it’s causing my anxiety to hit the roof. I’m waking up for work each morning wondering what’s it gonna be this time and feeling pits in my stomach. Please help. What are your thoughts on low-code platforms? I feel they will end up like WordPress (small companies with the tools in a varying degree of spaghetti that pay a contractor to clean up) I found myself on a team that wants to use it, and I feel like it’s a detriment to my career. I feel like another employer won’t take me seriously in an interview as I try to explain my way around it. Is this something I should be concerned about being in too long? I’ve voiced my concerns, but it doesn’t seem like direction is changing. What would you do? How do you feel about low-code in general?
Episode 347: New untrusting manager and crappy project management
In this episode, Dave and Jamison answer these questions: Our small team where I work as a senior software engineer has a new engineering manager. They don’t trust me at all and verify simple technical things like how git rebase works, in the middle of meeting calls. I feel micro managed. Calling me on slack (slack huddle) without prior notice breaks me out of my flow. Recently they called an “Architecture meeting” and ended up talking about 2 spaces vs 4 spaces and other trivial stuff. I just felt like the facepalm emoji for the entire time of the call. They are technically good, but lack depth. For some reason they think know better than everyone else in the team. Unfortunately, they are my boss. How do I politely tell them, in a professional way, that they have to back down and trust the team? Any help would be highly appreciated. Thanks a lot. Federico asks, Hi! I’m a junior engineer. Our project managers are really crappy. I keep getting wrongly managed and “exploding” projects, where in the last days everything goes wrong with the client. Should I take a project management course so I can organize better my projects and discuss with project managers how to prevent this? I don’t know how to make them work like they should.
Episode 346: Changing jobs with no raise and wrangling a cowboy coder
In this episode, Dave and Jamison answer these questions: I recently applied for a job for a great company. The interview went well until we talked compensation. I said I expected to get a pay raise for changing jobs, but it seems that they can only offer me as much as I already have. I have never negotiated salary before. With my current job (which was my first) I happily accepted what they offered and we have had regular bumps without negotiations. Although I am really interested in the job, I feel like it is a defeat not to get a pay raise when I’m changing jobs for the first time in my career. The benefits are also not as good. Do you have any advice? Should I lower my expectations for a non-consulting position and switch despite not getting a raise? Should I negotiate harder? Wait for something better? Hi Dave & Jamison, we recently started a new project with a new team of devs that never worked together before. The team consists of two experienced backend devs, two junior backend devs and a couple of frontend devs. One of the junior backend devs has a mindset of just jumping into tasks, doing things without any previous analysis, just writing code for the first thing that comes into his mind. I like him being proactive, but this is causing big trouble: bugs, technical debt and often absolutely useless code. We had several discussions in the team pointing out some of the problems, but he is not interesested in changing his behaviour. During the last discussion he didn’t react to any of our arguments, just insisted on doing things his way. After that discussion we realized he even made some commits on an issue that has not been in the sprint nor has been refined yet _while we were talking to him_. Our team has no dedicated lead nor a scrum master and we work remote only. The next organization level is our CEO. I love the company, i love the team, i love the project, i even like this dev on a personal level. If we talk to the CEO i suspect it might have a bad ending for the junior dev since he is still in probation period. I know that we must talk to our CEO if things do not change. Do you have any advice? How can we reach him? Thank you for your great show!
Episode 345: Head of Engineering vs writing code and Voluntary Severance
In this episode, Dave and Jamison answer these questions: I have around 14 years of experience and was recently promoted to a Head of Engineering role. I am now leading an engineering department of around 75 people. I’ve become increasingly ‘hands off’ with coding, and it’s been at least 2-3 years since I wrote code regularly. My role is completely hands off technically. I’m questioning whether this is the right role for me. I want be more hands on, but I worry my skills are now so rusty that I’d have to start over and spend all my spare time learning to code again. Do you think it’s realistic to get back to a hands on engineer role at this point? Have you seen it done successfully before? Does walking away from this leadership role make it harder to potentially take on other leadership roles like CTO in the future? Hypothetically speaking, let’s say that you were pretty sure layoffs were coming to your company even though they say they are cutting costs everywhere else that they can in order to avoid layoffs. Now let’s say that, hypothetically, in anticipation of this you took some interviews and received an offer from a company that you believe will ride out the upcoming economic downturn fairly well, and, hypothetically, you accepted the offer. Would you go to your manager and offer to take a voluntary severance, and in doing so, would you let them know you had something else lined up or would you leave that out and present it as just taking your chances while your severance checks were coming in? Thanks for doing what you do. Show Notes https://charity.wtf/2019/01/04/engineering-management-the-pendulum-or-the-ladder/
Episode 344: Showing impact without hiring and over over over engineering
In this episode, Dave and Jamison answer these questions: I’m a senior front end engineer at a medium sized tech company. During the good times of limitless tech growth, a common way for engineers to grow our “impact” (an important criteria at many companies for promotion) was to find ways to lead/manage more people, whether this was becoming a manager and having more direct reports, or becoming a tech lead and mentoring more people, especially interns and junior engineers. Now, with many companies doing layoffs and hiring freezes (mine included), teams simply aren’t growing and there just aren’t as many people to “impact”. What are some other ways to have more “impact” and grow my leadership skills? Both for hitting promotion criteria, but also for my own growth as an engineer that would like to be a manager or staff engineer someday. I am a very senior engineer at my company. There is an engineer on the team less senior than me, but not under me on the management tree. This person is well regarded in the organization, but has a strong tendency to over-engineer things. Normally I don’t mind a little over-complexity if it means that the person leading the project is taking ownership/accountability of the feature. But with this individual, they tend to be put in a place to make sweeping decisions that broadly impact systems when it’s clear that they don’t really have a full picture of what’s going on. To make matters worse… when I raise these points directly, the person will usually offer to accommodate my concerns by further over-complicating their solution/architecture rather than stepping back and picking an approach more appropriate for the problem. Show Notes This episode is sponsored by the original podcast from Red Hat, Compiler. Listen to Compiler: https://link.chtbl.com/compiler?sid=podcast.softskillsengineering
Episode 343: Tech lead/manager and discouraging seniors
In this episode, Dave and Jamison answer these questions: A listener named Mike asks, I’ve been offered an Engineering Management position at a company I previously worked for. The team is very small and composed of juniors and mid-level developers. The role is also completely new and because of the size and experience of the team there is some expectation that the manager will also have a fair amount of involvement in PR reviews and likely also writing some code. Is this common? Do you feel like a manager can also be a team lead from a technical perspective on a day to day basis? What should I be thinking about when considering this role? How do I keep up juniors’ morale regardless of bad code/ideas? I work in a team of 4-5 developers. We have one junior, one mid (me), one senior and our team lead. I think we mostly work well. However, sometimes the senior and team lead sort of talk down at the junior. For example, in a meeting talking about how to solve a problem the junior will propose an idea, but the senior and/or both team lead would respond by saying that no its not a good idea which is fine. However the tone of the voice often hints ‘oh you should know this it’s obvious you jamoke’. The junior has started to stay quiet and has told me he doesn’t feel comfortable asking the seniors for help. I’ve interjected in meetings to say I understand why the junior might have this idea but I don’t think it’s the best solution. What should I do? Should I talk to the senior/team lead? Do I just let it play out?
Episode 342: Losing my job to AI and bad review season
In this episode, Dave and Jamison answer these questions: Hello Dave and Jamison, thanks for your great work. Your podcast has the bizarre magical property of making me look forward to long drives. Keep it up! I have been feeling anxiety over losing my job to AI, especially after the all the ChatGPT stuff from a few months back. I know that it definitely isn’t flawless but I know that this technology will just keep improving as time goes on. I am a software engineer with 2 years of experience. I can’t help but feeling like I will lose this amazing career in the near future. I left my old line of work a couple years back and am in my mid 30s, so switcyhing careers again is a dreadful thought. Is there anything you can suggest to ease my anxiety? Will being more social with my coworkers, or aiming towards management help reduce my chances of being automated? Any advice will be great, thanks. PS: If someone tries to replace your podcast with an AI generated one I will boycott them and stick with you. It’s review season! I am an IC software engineer, and I am required to document my impact for the last year. However, I work on an auxiliary team/new business team that is always trying to find new use cases for the existing product platform. If you look at the numbers, the impact is very low compared to the core business. Also, my team was disproportionally impacted by layoffs late last year. Lot of folks with institutional knowledge and good relationships with the core team were let go which disrupted our team and contributed to missed deadlines. How do I write my review for this bad year, with little to show for it?
Episode 341: Offer rescinded and layoff stuff
In this episode, Dave and Jamison answer these questions: I am an American student finishing my undergraduate degree in computer science in the Midwest this semester. I am concerned about the economic climate of the technology industry. I am doing my second internship at a major technology company this summer (Microsoft). After that I will go to graduate school and try to ride out the storm. I have applied nearly a dozen programs including one year and two year masters programs, and even a few PhD programs (MIT plz accept me). My biggest concern is having my offer rescinded. I thought there might be economic turbulence, so last summer I had my return offer place me in the most profitable and highest growth division of the company. How do lay-off decisions get made on the issue of rescinding offers versus laying off people? How can I reduce the risk of the offer getting pulled? I am working on finding another software engineering internship, but it’s extremely difficult to find any open roles. Listener Andre says, I need a gut check here. I have a senior engineer on my team that does not perform well. He keeps procrastinating on tasks that I know wouldn’t take much effort. I think it would be great for the team and the company to substitute this engineer for someone with more passion. One idea I have is to volunteer this person to my director to be laid off. It would be great for the engineer to feed on the potential 3-month severance package. Firing him doesn’t seem like an option because he does the bare minimum for his role. What would you do?
Episode 340: Productivity lulls and code review showdown
In this episode, Dave and Jamison answer these questions: A listener Daniel asks, How do I handle periods of time where I am just not productive as I used to be? I’m talking about periods of several weeks. For example, when your kids are ill all the time (daycare fun) or you are down because of XYZ. How do you turn not really constructive feedback into useful feedback? I have a difficult time dealing with PR reviews from a specific colleague. They have a way to push my buttons somehow, it’s like even when they are actually right, the way they approach the subject or how nit picky their comments are just make it hard to take the feedback or start a healthy discussion. It prompts me to become confrontational. I know it’s not good to react like this, but I don’t feel comfortable talking directly to them about it to try to smooth things out. I don’t think its personal as I’ve seen this kind of comments on other people’s PRs too. I am aware this might be me being overly sensitive, but its like every time he is the one reviewing my PR I get the feeling of “oh, not this guy again” and need to mentally prepare for his comments. I’d like to find a way to take the core of the feedback that might be useful and kind of ignore the rest that might feel dismissive or opinionated, and I thought you might have some tools for this. The main reason I care about it is that this reflected badly on my latest performance review, as I had stellar feedback in general and the only improvement areas were that I should learn how to deal with mistakes or negative feedback better. I am aware it can be a weak point on me , but I know that a big part of that comment from my manager comes from my interactions with this specific colleague.
Episode 339: Coworker double-dipping and building toxic community
In this episode, Dave and Jamison answer these questions: I think the new hire on my team is juggling multiple jobs. On several screen shares, I’ve seen them quickly close IDEs with third party code, browser windows with what look like a third party jira instance, etc. Maybe that’s some open source project, or a jira instance where they’re reporting a bug, but it seems fishy. In the latest instance, this person meant to post a link to the Jira issue they’re working on in our company Slack, but accidentally posted a link to a ticket on some other company’s Jira. I did some digging and this is definitely not a public-facing Jira instance. It’s internal for their employees only. Normally if somebody could do both jobs competently, I’d say good for them and they’ve earned both salaries. However, their performance hasn’t been great. We’re still in the onboarding phase and a lot of missteps could be excused by that, but I’m starting to worry that this person’s goal is to offer only mediocre performance at this job (and probably the other one as well) and we’re unlikely to see expected levels of improvement as they continue to get up to speed. Am I being paranoid? Should I raise my concerns with management or give it more time to shake out? Is there a clever trap I can set to *prove* my suspicions for sure? I recently joined a large software defined telecommunication company, only to be surprised that their internal blind space is very quiet and very few ppl are on blind if any, how do I change this ? how do I get ppl to use blind more? without giving away my blind account. quitting my job is not an option due to the economy
Episode 338: I am the golden handcuffs and Staying in management
In this episode, Dave and Jamison answer these questions: Listener Mattoosh asks, I’m the last remaining support specialist on a really old, not actively maintained, but still lucrative SAAS product. I’m stuck. As a front end engineer I want to work on other projects within my organisation to gain contemporary framework skills, but nobody can backfill my workload. I know option A is “quit your job” but what other options do I have? I started my journey as an engineering manager at a startup. Over my stint, the company grew and so did the engineering team. Overall I received good feedback from the engineers but the founders didn’t recognize the value of this role and I felt that I wasn’t getting the required mentorship there to grow further. I ended up quitting. It’s been challenging to find another manager role. I get good feedback from the interviews but haven’t received an offer yet. I still am a good backend engineer but that is not what I want to keep pursuing. Appreciate any thoughts or suggestions on what I should do to bag one of these interviews as I don’t get that feedback from the panel. I don’t miss any of the podcasts and do enjoy the show.
Episode 337: Helping the principal and Manager conflict
In this episode, Dave and Jamison answer these questions: I am a mid-level engineer with ~5 years of experience (1 year at my current company). My team has recently hired a new principal engineer, and I’m wondering how I can help the principal engineer. There is, as always, some organization-specific context that I am familiar with, and the principal engineer is not. As a mid-level IC, I am not used to being a repository of knowledge for engineers that many roles above me, and have only ever been on a team that hired engineers at my skill level or below. Are there general tips on how to provide help for someone who has much more experience than I do? I have been in the industry for 5.5 years and have had 5 managers. My newest one (call them “S”) has been my manager for 4 months. Our communication is terrible. We do not understand each other and I am usually left feeling like I missed something or I am not interpreting his question correctly. I literally have told him “I am not sure what you want me to say” because that is better than “wtf”. I ended up crying in a meeting because I was so frustrated and confused. I know and trust my team mates. This is only the second time in my career where I just did not get along well with someone. The meeting was supposed to be some feedback for him and me, some career development, and some goals for 2023. It ended up with him giving lots of examples of technical deficiencies, the fact that I am unable to work independently (which is not true, I ask more senior engineers for help), the fact that I give him pushback (no duh why at this point). He even said I was careless because I made some silly copy paste errors in my code (which we all do and is human). [Sidenote: he does not code. He just sometimes asks questions on prs or gives nits.] I do not know what to do. His manager J used to be my manager. Should I talk to J about my issues since he knows both of us well? Do I go to my manager with ways that I would prefer our 1x1s go and how I personally like to get feedback? Do I ask for a new manager? I know he says he wants me to succeed, but nothing in the last 4 months have made me feel like that is true. I am a young woman in engineering, and I have never felt less trusted by a coworker. Especially the fact that I cried makes me feel like I may have lost more credibility to him. What do I do? Please help. I love my team. I just hate my manager.
Episode 336: Roadmap roadkill and returning to office
In this episode, Dave and Jamison answer these questions: Dear Dave and Jamison, I work for a medium sized startup, and our planning process sucks! We used to do quarterly planning, and it seemed like the product managers had no idea what was going on at a higher level. The big focus seems to have changed every quarter that I’ve been here, and the whole planning process is a charade: 75% of the so called ‘road map’ gets thrown away after a few weeks. Normally, this wouldn’t bother me, but I end up spending a lot of time in meetings helping these product managers come up with plausible timelines and making sure that what the business wants to build is actually feasible, and it’s bad for my morale to see so much of my work wasted. The product management team heard some of this feedback from me and others, and started changing to ‘continuous planning’, but now there is even less structure for when they build the big spreadsheet roadmap for the quarter. They bought new tools, and don’t seem to be using them. Should I suck it up and just check out or try and get a license to use the patented soft skills advice and quit my job? Hi Dave and Jamison in no particular order.I have been listening to the podcast for a couple of months now. I have enjoyed every episode and and the advice you give. I am a junior software developer who has been working at a startup 9 months ago. I was offered a remote junior position and accepted even though the company is based in a neighbouring city. This made sense at the time because I would not have to worry about commuting to the office. 3 months ago my manager suggested that I come to the office more often as this would benefit my development and give a me a chance to socialise with my co-workers. We agreed that I go in 3 times a week. Now the past few weeks there has been pressure to start coming to the office full time. I would be fine with this but the problem is that I currently do not own a car and have to rely on public transport to get to work. With public transport it takes almost 4 hours to get to and from work each day (I actually listen to multiple episodes of the podcast on each trip) There is about 40 minutes of walk time included in that because the nearest bus stop is not close to the office. As you can imagine that is physically draining and also affects my work life balance as I spend almost 15 hours of the day either travelling and working. My biggest concern now is that 9 months ago If I was offered this job but as full time on site I would not have even considered it. Do you have any advice with how to refuse going to the office more often without making it seem like I’m opting out of an option that is more beneficial to my career. Thanks in advance.
Episode 335: Senior questions and overly optimistic
In this episode, Dave and Jamison answer these questions: Greetings Jamison and Dave, love the show and all your shenanigans! I’m a mid-level dev who has quit my job (TM) a few times. While I feel like I’ve absorbed some good experience from each company I’ve been at, I also feel like my training is not yet complete. At my last company, I hit my ceiling as a dev but I also felt the bar was really low. I had to do a lot of hand holding and fielded a lot of engineer questions that could have easily been Googled and it was really frustrating. But now I’m at a place where I feel everyone else is heads and shoulders above me. The tables have turned! I’m trying to learn as much as I can on my own but I’ve found there are limits to what I can do. I feel like I’m drowning but I’m timid to ask too many questions because I remember how annoying it was to get pinged every 10 minutes at my previous job. What are some tips you have to navigate the murky waters of being a mid-level dev wanting to learn as much as possible to become a seasoned dev without giving off an “intern smell”? Listener Charlie, Nearly all your answers presuppose a software engineer has a good manager and leadership. Why is this?