
Free Daily Podcast Summary
by Jamison Dance and Dave Smith
Get key takeaways, quotes, and insights from Soft Skills Engineering in a 5-minute read. Delivered straight to your inbox.
The most recent episodes — sign up to get AI-powered summaries of each one.
In this episode, Dave and Jamison answer these questions: How long until I am ethically obligated to let my company know I’m doing no work? There was a big re-org at the company I recently joined. It’s a huge financial company, so there’s a lot of bureaucracy. Somehow in this mess I was kicked off the first team I joined so that I was pending re-assignment. It’s been a month and I haven’t been re-assigned. Instead of being in between jobs not working, I am currently in between teams, but still getting paid! This feels unintentional on the part of the company as no one has followed up with me. I’ve been happily using the time to catch up on hobbies, but I’m starting to get concerned about what will happen when the other shoe drops. At what point do I start to venture into irreversible reputational harm? For some added context, teams at this company are about 6 people and the manager handles several teams, so I’ve never talked to my manager since I joined. I got the message about the re-org from a screenshot of an email that my scrum master shared in my last stand-up. AI changes how software is build. Actual coding is mostly done by LLMs now (I hate it, but it is what it is). What do you think should I focus on learning now to not become obsolete in 1-2 years? I am a senior dev with 13yoe, and loved coding, but now I find it hard what my role will be in the next years (still have 30+ before retirement). I do not want to go to the EM track, at least not in the near future. So is it more architecture knowledge, security, AI internals, …? What do you think?
In this episode, Dave and Jamison answer these questions: Should I declare my struggle with this AI world we live in here? Nah. I mean, I’d like the hype to die down, a lot, but we keep getting new tools and I get to experiment, so here we are. My real struggle, and this podcast is implicated in it, is around non-technical people contributing to production systems. Why are we so obsessed with this idea? COBOL tried it. Low-code and no-code tried it. BDD and Gherkin aspire to it. Yet time and again the field demonstrates that you need people who know their stuff. To “democratize” software engineering implies that all people have the desire and ability to become software engineers. That premise is false. You democratize access to education or financial systems, the stock market say. You don’t democratize skill. Skills are earned. We would never, I hope, democratize bridge engineering or piloting an aircraft. Software engineers are just as critical as either. When our software breaks, money goes missing, electrical grids fail, information stops flowing. What I do think is great: now more than ever, as long as tokens stay cheap, people have more ability to build useful tools for themselves. But here is how I think about it. We have done tremendous work on literacy, and most people can read, but not everyone is an author. The same applies to code. anon e mouse asks, Should I share my tools? I keep building small local software tools to better test and debug the application I’m working on. The problem is that whenever I go “above and beyond” the assigned and expected work and try and responsible check it into version control and share it with the rest of the team, it gets bogged down in code reviews because it doesn’t meet the team lead’s vision because it wasn’t part of the vision! Once I go through that process though, it’s mostly appreciated, but the team lead is under a lot of business pressure and often mentions that we need to focus. Maybe I’m not focused enough, but many of these little tools are things that making verification and delivery much smoother! Like local testing utilities to verify and sample api endpoints that otherwise could only be called after prod deployments due to a lack of test data. Our partners like when we’re able to show the output before deployment, and the rest of the team usually struggles with that. I feel a pressure to hide my tools, but then I feel sloppy for having a bunch of useful tools outside of version control. These are things like formatting output, running experiments, testing data for variations. Am I unfocused or just bad at articulating the value of these tools?
In this episode, Dave and Jamison answer these questions: I’m approaching 15 years of experience with the last 7 years at fang. About a year ago I was promoted to staff engineer (thanks to the podcast) and switched to an adjacent team under the same director. I have never actively pursued a management role but I’ve been starting to think about it more. A colleague of mine just announced they need to take extended medical leave (1-2 months) and I was asked to fill in as a temporary manager while they are out. How do I go about managing a team if everyone knows it’s short lived? Should I just try to keep the team alive or aim higher? Is 1-2 months enough for me to get a sense of whether I’d enjoy management? I feel like I’ve dived into the deep end and it’s scary but also exciting. I love the podcast, I’ve listened to every episode! I’ll take whatever comedy or advice you have to offer. Bobby Drop Tables asks, Recently came out of a salary negotiation where HR blocked a payrise because they said I was already the highest paid non-management position dev. While I’m getting paid well for the market, I wouldn’t say it’s a ridiculous amount. HR said they wanted a fairly flat salary range across the organisation, with pay differences being dealt with via performance bonuses. On paper this sounds good for most departments (sales, engineering etc), but I’m really struggling to figure out what metrics management could use to assess the software team. It feels like any metric that could be dreamt up could/would be gamed and would likely have negative consequences. Have you ever come across any decent metrics or methods for assessing software performance when it comes to performance bonuses? Especially when the team lead might not have a say in who gets what or how much?
In this episode, Dave and Jamison answer these questions: I work at a large remote company. We meet up once or twice a year. I don’t really know much about my engineering coworkers aside from the 5 people on my team, so the in person meet ups seem like a good place for me to get to know people from the other teams. I am a career switcher, and am currently a mid level IC (borderline junior) in my late 30s and a youthful appearance. At these meetups, my position and appearance (and honestly, possibly my demeanour) makes me feel like I am expected to socialize with other ICs in their 20s. Although they are nice people I find it hard to relate to them when talking about non work related topics since I am much older and in a different stage in life than all of them, (married with a mortgage and kids). I want to socialize with coworkers closer to my age and stage in life but most of them are team leads or manager. I feel like socializizing with them would be seen as brown nosing. I’ve also heard that once someone is a manager, it is very hard for them to befriend ICs because they are now their boss, and that they mostly befriend other managers. My previous career had little management/corporate politics type stuff, so I don’t know if this is true. Would I be hurting myself by doing this? Am I over thinking this? Would I be fine socializing with whomever I want? Do you have any words or advice regarding my situation? Thanks! Hi Dave and Jamison, Before you tell me to quit my job, hear me out. I have worked in technology for about 30 years. I’ve been at the same company for the past 20 years, but I’ve changed roles many times to keep work interesting. I have enjoyed learning new technologies while working in development, architecture, system administration, management, vendor relations, and more. This has been very beneficial to my career, and I appreciate all the opportunities to grow. I’ve earned a good reputation and am well respected by my peers. I’ve proven my worth to leadership many times over by reducing expenses by many millions and creating innovative solutions to improve efficiencies. I work for corporate America in the insurance/finance industry, which is generally considered to be led by cold, heartless, power-hungry mongers, a stereotype that probably has a few exceptions but is generally not incorrect. I’ve never appreciated this industry’s business practices, but I’ve had to make a living over the years, so here I am. I am finally at my breaking point and am absolutely fed up with how employees, customers, and communities are treated by my industry. Because of this, I just cannot find value in my work. I’ve been beaten down over the years and am tired of being exploited by management. I no longer volunteer to take on big projects, and instead of being someone who outshines others, I have decided to settle for mediocrity. I’m planning to retire in a few years and honestly don’t have the energy or desire to search for another, potentially more meaningful, industry to work in, especially in the current job market. I genuinely care about many of the people I work with. Very few of them are in it to climb the corporate ladder. Most are just trying to earn enough money to pay the mortgage, feed their children, care for aging parents, and hope to have enough leftover for their own retirement. How do I not leave a wake of malaise for my peers when I leave but also not help feed the beast until then?
In this episode, Dave and Jamison answer these questions: I am a senior software engineer at big tech and need a career change. With the rise of AI, I no longer enjoy this profession and panic everyday just waiting for a huge round of layoffs. At this point I feel like I am on some assembly line hitting enter like a monkey. Therefore I have been thinking of changing lanes and would like to get into engineering management. On the one hand I have enjoyed mentoring, strategic planning and coordinating projects across vendors and across teams, but besides that I don’t have clear evidence that this profession would fit me. In my current job there is no immediate opportunity to step up and manage a cross team project at the moment, so I am not sure how I can figure out if engineering management is the right choice for me. How do I figure this out without doing the job and how does one transition into it, probably as an external hire or transfer hire? Paolo asks, I’ve stepped into a senior role recently. I’m no longer the primary driver on projects. I’m supposed to create space for junior developers to lead, make decisions, and own outcomes. My job is to mentor and support, not to take the wheel. But I’m seeing projects drag because of passivity. Sometimes the solutions are inefficient. Other times it feels like the core problem isn’t fully understood before execution starts. In a few cases, momentum just stalls, and weeks go by without real progress because no one is pushing the work forward. It’s worth mentioning that I check in multiple times to offer help yet these problems keep happening. I believe people grow by struggling, so I don’t want to jump in at the first sign of friction. But if a project slips or fails, that responsibility ultimately rolls up to me. So how do you strike the balance? How do you give someone real ownership, not just symbolic ownership, while still maintaining standards and accountability? And how do you avoid becoming either the micromanager who swoops in too quickly or the absentee leader who lets things drift?
In this episode, Dave and Jamison answer these questions: How can I get our company to follow the law and stop sending SPAM without being regarded as negative? We’re sending out emails that don’t comply with CAN-SPAM, and I think we should comply due to the risks, but I don’t want to risk any blowback! People want the emails to look more ‘human’ sent, and putting your mailing address at the end of an email is not very human, so we’re not doing that… It’s a medium startup (500 people), but I’m close enough to the marketing work that they might know it was me! Should I send an email to our general consul? How can I raise concerns and do the right thing without being regarded as not a team player?? How do I stay motivated on a team that’s always sick? I’m on a team of 3 ICs and one manager. The other two ICs are plagued by health issues. I am trying to be empathetic, but this has been going on for the at least a year. One of them regularly takes sick days, often turning into sick weeks. The other has a long term issue and regularly does half days. This affects our ability to produce results, but we don’t have a PM and don’t really have deadlines given the nature of our work, so it’s not really noticed. I feel like we are moving a lot slower than we could be, and when we do check-ins on our goals at the end of each quarter, we maybe only hit like 50% of our goals. To me it’s quite obvious why we don’t hit our goals, but everyone else seems to be surprised by it. My manager can’t manage with enough rigor to produce results. I’ve brought this up to them before (our goal misses, not teammates being sick), but nothing seems to change. As the only seemingly-healthy member of the team, there’s no incentive to work more than the bare minimum. I feel like I should be taking more sick days! This is very demotivating and I feel like I’m stagnating. How would you all approach this situation? Should I also suddenly have health issues? Is this actually a blessing in disguise and I should make the most of it? Show Notes https://overcast.fm/+ABLmzfhZxak
In this episode, Dave and Jamison answer these questions: Hey there, I started a new job in August at a large European retailer. There were ups & downs, but long story short, my weekly one-on-ones with my manager was either positive or neutral. This was my second job after graduating, so the firm factored in, I’d like to think, when setting expectations this was my first time switching codebases and tech stacks. On January 3rd, I was fired in the last month of my 6 month probation. This was a total surprise. My tech lead told me I required too much assistance from others to finish my tasks. Some part of me doubted the sincerity of my boss, since I asked for example pull requests or tickets where this was the case and he was unable to provide a single example, but obviously, like every dev, technical insecurities are a big part of my life. I’ll be starting a new job at a prestigious newspaper in May, so here’s my question. In a remote first environment, how do I determine if I’m meeting expectations? How do I gauge my standing in my team? How do I avoid a repeat? How do I effectively integrate myself into a codebase? Disclaimer: At the end of January, everyone in my department was hauled into a meeting and was told the retailer hired 11 external, Portuguese developers to ‘finish the job’ since management wasn’t happy with the output of the 9 internal developers (aka nearshoring) and no internal would get a pay increase this year. My tech’s boss was also fired/forced out/quit before he could be fired. Trevor asks, How do I balance depth with breadth? At my current job, I am moved around projects/code bases all the time and I am exposed to a variety of technologies and subareas. That’s cool but I feel like I only manage to face the consequences of our choices for a couple months until I am moved again. I think I need more time to really become an expert in any one area. At the same time, I dread getting stuck in maintenance work. It seems like most people around me (at my company or outside) find it boring and soul-sucking, and are only excited about major projects from scratch. Does a job that has a good balance of both exist and if so, how do I find it?
In this episode, Dave and Jamison answer these questions: Hi Djavison, I’ve heard y’all say something along the lines of “this is the most exciting time to build software” in a few recent episodes. I’m glad that has been your experience and seems to be the experience of many others. But for me as someone 5 years into the career who is, thankfully, employed—I can’t help mourning a job that no longer exists. Obviously, there are still lots of us with the job title “software engineer” that create software. But, what I originally fell in love with doesn’t really seem like a thing you can get paid to do anymore. I now spend most of my development time reviewing code and making sure things work. Which feels way less rewarding and way more soul-sucking. Maybe I’m just nostalgic for being a more junior developer, but it’s obvious that our jobs have changed forever and will continue to evolve. So, my question is: How can I get excited and feel passionate about this new way of doing things? I am a senior team lead with 10+ years of experience. This is the first time I’ve had a team mate that clearly disrespects me. I have a Middle+ teammate who is technically perfectionistic and openly says I’m doing a poor job and that basically he doesn’t see me as an authority. He says I am not as devoted to technical excellency and improving the project as he is, and that I ignore his opinions, which is his term for not having the same opinion about tech stuff as he does. He doesn’t see the big picture and thinks he’s the only person on the team trying to make the code better. But the worst part is he never admits he’s wrong. I had to scramble to fix a bug he created when we caught it right before release, and he accused ME of introducing it! My manager know what’s going on, but I feel terrible about it. I have many different projects and responsibilities. I can not be as devoted to the codebase as he wants. Plus, I am not the architect and nor should I be. I see that it demotivates him (like the person in the 499th episode), only in this question I am the senior. I know my weaknesses and I am working on them, I don’t think I can address his feedback. More than that, I’ve always tried to maintain a good relationship with him and always gave him the freedom to work on tech stuff and develop his skills. But what to do when your child has grown and is now unthankful? 😂 Thanks for your advice!
Free AI-powered daily recaps. Key takeaways, quotes, and mentions — in a 5-minute read.
Get Free Summaries →Free forever for up to 3 podcasts. No credit card required.
Listeners also like.
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.
AI-powered recaps with compact key takeaways, quotes, and insights.
Get key takeaways from Soft Skills Engineering in a 5-minute read.
Stay current on your favorite podcasts without falling behind.
It's a free AI-powered email that summarizes new episodes of Soft Skills Engineering as soon as they're published. You get the key takeaways, notable quotes, and links & mentions — all in a quick read.
When a new episode drops, our AI transcribes and analyzes it, then generates a personalized summary tailored to your interests and profession. It's delivered to your inbox every morning.
No. Podzilla is an independent service that summarizes publicly available podcast content. We're not affiliated with or endorsed by Jamison Dance and Dave Smith.
Absolutely! The free plan covers up to 3 podcasts. Upgrade to Pro for 15, or Premium for 50. Browse our full catalog at /podcasts.
Soft Skills Engineering publishes weekly. Our AI generates a summary within hours of each new episode.
Soft Skills Engineering covers topics including Technology. Our AI identifies the specific themes in each episode and highlights what matters most to you.
Free forever for up to 3 podcasts. No credit card required.
Free forever for up to 3 podcasts. No credit card required.