TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Software How-To

    Soft Skills Engineering – Jamison Dance and Dave Smith

    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.

    Advertise

    Copyright: © 2016 Jamison Dance and Dave Smith

    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    Episode 324: Understanding accents and mega soft skills Oct 03, 2022
    Show notes

    In this episode, Dave and Jamison answer these questions:

    1. I’m currently a junior engineer. I often struggle to understand speakers with accents. I became aware of this when I listened to a coworker in a meeting and barely understanding anything, but when I asked my other colleagues, it seems they got it completely.

      I know how to handle this in relaxed situations, but how do I handle it when the stakes are higher? (i.e. talking to higher levels and not wanting to ask too many questions based on my inability to hear them, interviews, …). How should I prepare to respond to these situations productively?

    2. Hey fellas,

      As a backend dev of 3 YOE, I have what I would describe as average technical skills and much stronger than average soft skills. This has been reflected in my feedback across all of my jobs and while the feedback has always been very positive, almost all of it relates to my interpersonal and communication skills, as opposed to my technical chops.

      I’m wondering what’s the long term outlook for this is? I frequently receive more accolades and recognition from leadership than my colleagues whose technical skills and code output are objectively far superior to mine, simply because I communicate better and am more charismatic

      Given management’s favorable view of me, I have been ascending the ranks quicker than is warranted, beating out those that are much more qualified from a technical perspective. While I am able to complete the work that’s asked of me, I can’t help but wonder when I will stall as a dev and no longer be able to meet expectations, nor is it really fair to anyone involved.

      At this point, I can’t help but feel that I would be able to contribute more in a position that utilize my skillset more favorably, but I’m unsure what roles would be a good fit for someone like myself.

      Thanks guys!


    Episode 323: Shopping offers and returning equipment Sep 26, 2022
    Show notes

    In this episode, Dave and Jamison answer these questions:

    1. I’m planning to leave my job purely because of low compensation. I like my growth in my current company - but low compensation than what market is offering is quite a mental hiccup in my regular work (yep! I’m slowly becoming one of the quiet quitters). I’m thinking of going to my manager with my new offer and ask him to match it. Do retention offers actually work? As mangers yourselves, how would you want me to approach a retention discussion? I don’t want my manager to make my life hell under the pretense of “Oh he’ll leave in a year” if I do decide to stay after taking the matching offer. Love the show - pretty much my single source of wisdom for all my behavioural interviews xD

    2. I was recently let go from a company. They said they would send me a shipping label so that I could return the hardware. I didn’t hear back from them for a week. A few days later a label came in for the laptop, but not for the dock or the two monitors they also sent.

      I did not enjoy my experience there and I’m feeling resentful at having to pester them so that I can get what I need to send them back their hardware.

      What is my due diligence on the score? I don’t even like the monitors.


    Episode 322: Cover blown and no one cares Sep 19, 2022
    Show notes

    In this episode, Dave and Jamison answer these questions:

    1. Listener Olexander asks,

      I was a tech lead on some relatively known project since the beginning for more than a year. I made several trade-offs with technologies and wrong decisions. I participate in some generic Slack organisations and met several users of my product. I haven’t told them that I was connected to implementing the project but sometimes shared some insights on how the product is tested and asked opinions about some of features of the product in comparison to the competitors. Now there is a person who continuously critiques the product. Sometimes the criticism is valid but sometimes is’s just a rant. How can I influence that person without blowing my cover?

    2. Listener Kieran asks,

      Hi guys! Loving the podcast from down under. I’m working part time as a dev while I complete my software engineering degree. It’s been fun, but there are almost no processes in place for development and not many other devs seem to care about improvement.

      Although I am the most inexperienced here I feel some of the devs do not care about the quality of the work as I often have to refactor some of their code due to it being buggy, slow and undocumented (still using var in javascript).

      I’ve talked to management about improving our standards. However, they brushed me off saying yeah some of the developers are stubborn. They are not brushing me off because I lack technicality as Ive been given an end user app as a solo project. How should I go about encouraging the team to improve our processes?


    Episode 321: Politely, no and participation at scale Sep 12, 2022
    Show notes

    In this episode, Dave and Jamison answer these questions:

    1. How do you politely tell a reviewer politely, “Your suggestion is stupid. I will not do it” when you get stupid review comments. If you don’t do it then the pull request can’t move forward because of unresolved issues. If you do it, then you’re compromising your design you’ve worked weeks on for some fly-by random comment.

    2. A few months back, I volunteered as co-facilitator for my department’s NodeJS Guild meeting. At first, it was a struggle to get people to present. But I tried to lower the bar more and more until it was easy. I asked for 10-15m presentations, and eventually I realized people are happier “Kicking off a discussion” than they are “giving a presentation”. All the listeners are more engaged too, at least after the first 2 meetings doing this.

      Now I want people to share half-baked code, or problems they are struggling with, as part of our discussions. I want people to be able to be vulnerable. If we don’t collaborate on common problems until we feel they’re polished and won’t reflect badly on us, then we will all waste time solving the same problems.

      I also want this to scale across 15-25 small scrum teams. I think success could be my demise–if we have good discussions, then more people will come, but people won’t want to be as vulnerable with a larger group.

      In general, I think my own scrum team is very open and vulnerable to each other, but the remote work in the deparment has created distance. I want to help create more collaboration on similar problems and solutions.

      What would you do to keep this going, and improve it?


    Episode 320: Hot and less hot and no privileges Sep 05, 2022
    Show notes

    In this episode, Dave and Jamison answer these questions:

    1. I seem to be very hot and cold about how I feel about my job. Some days I hate it and think about quitting, but other days, I feel it’s not that bad and can stick around a little longer. The reason for it seems to change depending on the day, but a lot of it seems to center around the people around me (i.e. developers who need me to Google for them, business people who don’t understand how to provide requirements), but sometimes I can’t tell whether it’s an attitude problem that will follow me anywhere or if it’s just time to leave. It’s a relatively small company, so I feel like I would be betraying my manager who has invested a lot in me if I decided to leave so suddenly. I’d like to give my manager a chance to address my concerns, but I’m afraid to sour our relationship if I come across as a complainer. I’m also not confident there’s any solutions to my current frustrations because it seems to be a company-wide issue. How do I make sense of all of what I’m feeling?

    2. I really like my company but their project management is atrocious, ad hoc, and “old school.” They’re not giving me privileges to configure Jira in ways that allow me to get stuff done.

      Is there an effective way to convince my CTO that I’m not going to screw up our secure systems or do I just need to find a new job?


    Episode 319: Steve's babysitter and these uncertain times Aug 29, 2022
    Show notes

    In this episode, Dave and Jamison answer these questions:

    1. My company wants several complex applications rewritten. “Steve” wrote the original applications, and has been assigned to do the rewrite. There is very little documentation on the original applications, and the rewrite will take intimate understanding of the existing code and new requirements.

      Management assigned me to work with Steve. They warned me that since we have started working remotely after covid, Steve has been hard to get a hold of and not meeting deadlines. My job is to keep Steve on task.

      When I ask Steve a question he will respond “I’ll work on it tomorrow” or “I’ll have to look in to that.” Then I never hear from him again. If I tell management I haven’t been able to get a hold of him, they will contact him, then he will contact me asking “What can I help you with?” Again, all his answers will be “I’ll have to look into that.”

      Occasionally Steve will report to me that he has finished a task. But because he did it without me, I am even more confused about what needs done or how to do it.

      I feel like my job has turned in to tattling on Steve. I am afraid I’m going to be labeled a whiner and that this project will harm my career growth.

      Over the last 2 weeks my solution has been to just ignore the project. Management hasn’t checked in with me, but I’m sitting on a ticking time bomb.

      What should I do?

    2. How to keep our sanity in times of uncertainty? I’ve recently changed jobs and despite the facts shows that I shouldn’t be worried, I can see my judgement is blurred by the fear of getting laid off even there’s no sign of it and I fear I would fulfill the prophecy!


    Episode 318: Staff and part time dev Aug 22, 2022
    Show notes

    In this episode, Dave and Jamison answer these questions:

    1. Listener Albert Camus asks,

      Hello Team. I am a long time listener of the show, and I really enjoy it. I’m a senior engineer and want to get to the next level in my career. I talked to my manager about this. I told them I preferred the technical side and staff engineer was the next level up. He responded positively, although he didn’t give me a timeline, not even a vague estimate. In a subsequent meeting they told me it wasn’t a linear progression at the company and there’s quite an overlap in the salary range between senior and staff engineer. I was also told that the company only had a few staff level engineers and they were considered experts at a particular sub-section of a technology. This makes me feel like I am being stalled. I have seen this a few years ago, at a previous workplace, where I tried for a promotion, and the manager at that place kept giving excuses to buy time. I am afraid that could be the case here as well. I am technically strong and have good soft-skills. I have designed, developed and documented multiple features for the company. Whenever there’s a complex bug, the product manager always turns towards me for help. I also handle inter-team discussions at times, always a part of the interview panel while hiring new team members and at most times the only person representing my team from the tech perspective during alignment meetings with the sales and marketing teams. I could also say with confidence that I bring more value to the table and have data to back it up. But I am not sure how I could use all this information without seeming desperate, to really push for that promotion and a raise. I could quit and get a new job, most probably with a promotion, but I have put in a lot of effort here and I intend to stay at the current company for at least the next couple of years to reap the rewards. What can I do to get that promotion in the coming year?

    2. We know that the salary is high in our area, and I don’t need all this money. So, what is your opinion on part time job and how can I get one?

      I’m a senior frontend with more than 15 years of experience and just want to live a little.


    Episode 317: Process renegades and hiding my disgrunteledness Aug 15, 2022
    Show notes

    In this episode, Dave and Jamison answer these questions:

    1. I work at a small company that has recently grown from a couple of engineers to 40+ due to some great new project opportunities. As part of this transition, many new policies are being implemented. The policies concerning the engineering department primarily revolve around task tracking and reporting time. Gone are the days when an engineer can charge eight hours to “fixing stuff” and earn a paycheck. Most of us are on board, but there are three engineers in particular who have been around for quite some time and vary between subtly passive aggressive to downright combative when it comes to creating JIRA tasks and logging their hours.

      The problem? They serve an absolutely critical role in our company. They are nigh irreplaceable in an extremely niche market. How should a manager strike the perfect balance between forcing an engineer to do something that they don’t want to do and not forcing them out? If this was a more common skillset, there wouldn’t be an issue with telling them “You don’t like it, go find another job”. But when there are a handful of people in the world that do this kind of thing and it closely involves hardware and these three just happen to be local… well, you get the idea. Losing these individuals would be a staggering blow the company. Making them redundant isn’t economically feasible. Time to ramp up for this position would be close to a year.

    2. So I’ve recently followed the first rule of Soft Skills Engineering and quit my job. All right! I believe in the new role and I think it’ll be a good change to me.

      Despite this, I’m feeling guilty about leaving my team behind. When my managers asked me how I was feeling in the last few quarters, I’ve mostly said I’m fine! I never told them my reservations about how the codebase I’m working on has no oversight, that they need to hire another dev because I don’t trust being the sole keeper, that it seems like product has forgotten this feature. I even indulged them when they asked me to make a long-term career plan when I was certain I would leave by early next year at the latest.

      So, what’s your take on how disgruntled employees often have to hide their true feelings? Maybe I could’ve been open, but it really seemed like the odds were against us, it’s just that upper leadership was neglecting this feature and there was no urgency to improve things. But I still feel like I wasn’t being fully honest. What do you guys think?

      Thanks so much and keep up the good work! Feelin’ Guilty

      P.S. Do you feel that this industry naturally rewards lack of loyalty and connection? What do you feel about that?


    Episode 316: Skills reboot and quitting the perfect job Aug 08, 2022
    Show notes

    In this episode, Dave and Jamison answer these questions:

    1. Hi! I have been a software engineer at a very small company for 10 years. We write desktop products and single server products - I don’t have experience with scaling systems or the latest & greatest Javascript frameworks. I would like to move to a company where I can learn and grow, using a more modern stack. My coding skills are great, but it seems like I just don’t have the experience many companies are looking for. With 15 years total experience I am too junior for senior positions, and too senior for junior positions. I’m feeling stuck and am tempted to quit my job so I can focus on side projects using the latest and greatest tools. Or is there a better way to get unstuck?

    2. Listener James asks,

      How do you know when it’s the right time to move on from an almost perfect job?

      I’ve been a frontend developer for 6 years and spent the last 2 years at a really great company. I have lot’s of autonomy, a competitive salary, excellent stock options, and great job security. But, so far my entire career has been working with the same technologies, and there’s no scope to learn new languages at my current job.

      I was recently contacted by a recruiter, which resulted in an interview and offer for a full-stack role with a stack that would be completely new to me but really excites me.

      I’m worried that never holding development job for more than 2 years would look bad, but at the same time I don’t want to be stagnant and not learning.

      Should I stay at my current job where I’m comfortable, or take a risk and jump into the unknown to develop my career.


    Episode 315: Poor feedback recipient and rubber duck Aug 01, 2022
    Show notes

    In this episode, Dave and Jamison answer these questions:

    1. Do you have any advice on how to give feedback to people who don’t take critical feedback well? There’s a person who joined my team with the same job title and level as me (senior product designer/L5) more than a year ago, and since then he has shown that he not only lacks a lot of skills to be considered senior but also lacks the self-awareness to see where he falls short and how he needs to improve. There have been multiple occasions in our 1:1s where he has alluded to critical feedback he’s gotten from people on our team (including our manager) and has written it off as irrelevant or untrue, will come up with excuses for his poor performance, and will make off-hand comments about the person as a way to discount their credibility. Overall I feel like this is part of a larger display of narcissist behavior; I’ve noticed that the only time he’ll listen to suggestions is if you make it not sound critical and sandwich them in between compliments.

      Up until now, I (hopefully) have avoided being on the receiving end of his negative comments, but since I’m trying to go for promotion, my manager wants me to give him more guidance and tell him directly the feedback that I’ve brought up to her. Seeing how he’s reacted in the past, I’m unsure how to just start giving him unsolicited feedback and am afraid of what he’ll think and say to others about me as someone with four less years of industry experience trying to give him advice. I’m also afraid that this will damage our working relationship as I’ve seen how despondent he becomes when things don’t go his way. I’ve told my manager these concerns and her response was that it isn’t on me if he reacts poorly to my feedback, but I feel like putting in the energy to give him feedback that he probably won’t even listen to is exhausting and isn’t worth the possibility of him becoming more adversarial towards me. What can I do? Any advice??

    2. I recently joined a new company following the patented space law certified strategy of quit your job. I have a senior colleague who has been there maybe 8 months more than me. Whenever he has a problem, he likes to call me away from my desk and start explaining his entire problem to me. I have no knowledge of the real codebase yet and am not even an experienced programmer as I barely have 2 year of experience. I just stand there and nod and give various quips from time to time to pretend I’m listening. This can last up to 30 minutes and happens numerous times a day. If I say I’m busy he just waits 5 minutes before calling me over again. I cant get any work done because of this. How do I deal with this senior team mate that uses me as a rubber duck. Should I just buy him an actual rubber duck ?


    Previous 1 20 21 22 23 24 54 Next

    Related Podcasts

    Know How… (Video)

    1

    Know How… (Video) Education
    JavaScript Jabber

    2

    JavaScript Jabber Education
    Programming Throwdown

    3

    Programming Throwdown Software How-To
    Software Engineering Radio – the podcast for professional software developers

    4

    Software Engineering Radio – the podcast for professional software developers Software How-To
    The Changelog: Software Development, Open Source

    5

    The Changelog: Software Development, Open Source How To
    Coding Blocks

    6

    Coding Blocks Software How-To
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights