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.

  1. 5日前

    Episode 480: Do I just coast until I quit and going back to work after a long time

    In this episode, Dave and Jamison answer these questions: (follow-up from question 449) Hello. Return question asker here. You answered my question from episode 449 “my tech lead ignored my warnings”. I want to give a follow up. I sat by and did not say anything else, he shipped the broken feature, and it broke in production. Instead of fixing it he rose the threshold on the datadog alert so high no one would ever get alerted. Then he left the company. When talking to my manager about the bug we agreed it was part of that refactor and I said “I warned him” and they shrugged it off. I assume he is also a long time listener of this podcast and took the age old “leave your job” advice. Kudos. (question below) I am here for more than just an update though. I am starting to think I understand why he left. It sucks here. I am the lowest level engineer on my team and have not been promoted for the last 2 years because “there is no money”. Ok, fine, I understand that the economy is tough. However I have increased the revenue of my department by 4x, have lead the development of our flagship product this entire year, have been teaching engineers new technology and have been working 60 hour weeks. On a team of 6 I do 33% of the work. 2x what is expected of any one engineer. This last week I received a “meets expectations” performance review. And I am mad. In 1-1’s with my boss they explicitly tell me “I am not saying to sandbag but just do less work. Your teammates are getting compared to you and its making everyone look bad.” Don’t worry Dave and Jamison, I am going to quit this job so I don’t need that advice, however you can throw it in if you like, but I’m wondering how do I handle this? Do I confront my manager in the next 1-1 with the data and say I am underleveled and underpaid or do I just take the advice to do less and coast til I find another job? Do I share with HR in the eventual exit interview that this was the straw that broke the camels back? I’m returning to work after a very long absence due to personal issues. How can I ramp back up quickly? It’s a weird situation because I’m not exactly joining a new job, but it’s been so long that it basically is. I haven’t even opened a code editor in months!

    27分

  2. 9月22日

    Episode 479: Contractors to the rescue and dinged for delay

    In this episode, Dave and Jamison answer these questions: Hey skillet nation, long time skilletee first time skilleter here. I started at a scale up about 6 months ago and recently, I was asked to help with a project that was greatly behind schedule. The folks responsible for the original system are no longer at the company, and the team currently attempting to get it over the finish line have struggled greatly. The codebase is full of performance issues and the infrastructure was not set up to scale. Basically things are bad. Since joining, I’ve helped draft a plan to fix most of the performance issues, and then incrementally improve the architecture. Things are going great, except for the fact that we’re 6 weeks out from our deadline with a burnt out dev team. To resolve this, our CTO hast started to rapidly hire contractors to “help out”. As one might expect, this has only slowed us down. But our CTO, lacking trust in the previous team, has found the promises of the contractors very alluring. I, on the other hand, don’t love the idea of building this greenfield system with temporary workers and then dropping it on an already burnt out team to maintain. Am I overreacting? How would yall handle this scenario? How can I convince our CTO that “the mythical man month” still applies here, regardless of what the contracting company says? Listener k pop demon hunters asks, Hello! I’m a senior engineer in a big tech company. I recently got a bad annual review from my manager due to the fact that I caused a delay happened in my last project. It was a compliance process involving multiple stakeholders and one of them didn’t give me an immediate approval for the step they owned. I promptly updated my submission for review after I got the initial feedback, pinged them in a messenger and sent a reminder mail every day until I got an approval from them. I feel absurd that I got a bad review due to the delay of external process. What could I have done this better? Thanks for the great show. It’s making my commute more enjoyable. Keep it up!

    35分

  3. 9月15日

    Episode 478: Can you coach self-awareness and my boss is an llm

    In this episode, Dave and Jamison answer these questions: Can you coach self-awareness? I manage someone who seems to believe their skill set is on par with their teammates, regardless of their constant PR feedback regarding the same issues over and over, the extra attention they are regularly given to help them overcome coding challenges, and the PIP they are currently on to address these issues (and others). What are some approaches I could take to help steer them to better understand their areas for growth when explicit measures don’t seem to get through? I work at a small 10-person startup. The company has absolutely nothing to do with AI, but one of the founders has gone full evangelist. He genuinely believes AGI is arriving this year and that there isn’t a single job, task, or process where an LLM isn’t the obvious tool. Day in, day out, he’s posting links to random AI products with captions like “looks interesting 👀”. It’s like Clippy got a16z funding, moved to Shoreditch, and now spends his days flogging us apps we didn’t ask for. He also insists we “use AI more in development,” despite not understanding development in the slightest. The routine is always the same: He asks the engineering team how to achieve some goal (always involving an LLM). We give a sensible answer, weighing complexity, cost, feasibility. He comes back with a massive pasted transcript: “here’s what ChatGPT thinks.” We pick out what’s actually useful, quietly bin the nonsense. He takes our response, shoves it straight back into ChatGPT, and returns with another transcript: “here’s what ChatGPT thinks.” This has been going on for months. At this point, he’s basically a human middleware layer for ChatGPT — no analysis, no original thought, just endless copy-paste recursion. I’m genuinely worried he’s outsourcing his entire thinking process to a chatbot and slowly losing the ability to engage with ideas on his own. How do I tell him — politely but firmly — that this is both rude and a bit tragic? And, half-serious: is there a prompt injection I can use to jailbreak my founder back into being an actual founder rather than a ChatGPT relay bot?

    38分

  4. 9月8日

    Episode 477: Four months and I already hate my job and grumpy and fuzzy

    In this episode, Dave and Jamison answer these questions: Hey guys, I have been working for four months at my job and I already don’t like it. This is my first job out of college and I work as a C# backend engineer for a small B2B SaaS company. I really think this company is a dead end. There is a lot of technical debt and antipatterns and we have no automated testing whatsoever. Most of our time is spent manually debugging but no one wants to refactor. I’m already thinking about working somewhere else. However, it took me a while to get this job, and I don’t think the market has gotten any better since. I’m trying to decide whether I should focus on applying to jobs again or if I should work on a bunch of side projects and open source to stand out better. On one hand, I can learn new technologies on my own to make me stand out for my next job, but on the other hand, I feel like as long as I stay at this company I am wasting time, since I’m not learning from my job. I want to switch to more distributed backend engineering in Java anyways, but I’m not sure how to go about it. Listener Ghani asks, “I’m a mid-level software engineer who has trouble communicating with my engineering manager and product manager when there is unclear or missing information about an assignment/story/project. They answer with hostile/dismissive tone/non-answer (e.g it’s on the jira-card, epic, etc). They course correct when they have the information later, harshly my impressions were they don’t have the information at the time they expect engineers to make decision they expect engineers to know something they don’t (e.g architecture, infrastructure, past decision, plans, etc) I really want to look for where we can have a safe exchange of information. How can I do this?

    38分

  5. 9月1日

    Episode 476: How much help is too much help and guarding against slop

    In this episode, Dave and Jamison answer these questions: Two junior engineers recently joined my team, and I’ve been tasked with onboarding them. This is the first time I’ve been responsible for junior devs, and I’m struggling with how to coach them up. For context, we’re a small engineering team where self-sufficiency is highly valued; processes/overhead is minimal, and we have a real bias for action. As such, when they ask me for help, my intuition is often to respond “Keep looking, figure it out!”; in my mind, walking them to the answer would be anthithetical to our culture and set the wrong expectation for how they should go about solving problems. This is especially the case when they throw their hands up and say “Help, I’m stuck, what do I do”. Though, I don’t want to be so unhelpful that it frustrates them or legitimately impedes their progress. I’ve also noticed them sometimes going “behind” me to ask others engineers for help, which makes me think that I am being too unhelpful. The number one question I ask myself is: How much help should I be giving them? How do I find the right balance here? I’m seeing more and more AI slop in my org’s code base that I fear will have meaningful impact on the integrity and maintainability of the application we deliver to customers. Everyone talks the talk of “Ultimately, it’s the implementer’s responsibility to audit and understand the code they ship,” but few seem to walk the walk. How can I best work with my team to address this, especially in a context where leadership is prioritizing velocity?

    38分

  6. 8月25日

    Episode 475: Am I too loyal to my big tech job and politely preserving time

    In this episode, Dave and Jamison answer these questions: Hi! I’m currently working for a big tech company and I’ve just accepted an internal transfer to another team. At the same time, an external company reached out, offering me a job for a role I’m interested in and twice my current compensation. I’m not sure what to do. The offer from the new company is very interesting and I wouldn’t think twice at accepting it if I still was in my old team. But now that I’ve accepted the internal transfer, I don’t know what’s best for my career: stay with my current company and lose out on a great offer, or go with the new company but likely burn bridges with my current manager, possibly closing off future opportunities to return to my current company (something that I’m open to in the future)? How do I politely but firmly stop a project manager colleague, who has vast open plains in their calendar compared to my Tetris-stacked week as a senior software engineer, from parking themselves at my desk for 45-minute vent sessions about everything that’s frustrating them about our project? It’s never just the weather; it’s a full-blown TED Talk on their annoyances, which makes me feel defensive and frustrated in return. I’ve tried the headphones-on-and-look-intently-at-the-screen-approach, and sitting on the other side of the office, booking a smaller meeting room to hide, and carrying on working as they tell me about their troubles with both leadership and members of my team. Nothing seems to work. They find me every time. Is there a way to escape without faking my own death or staging an office fire drill? Thanks!

    33分

  7. 8月18日

    Episode 474: I hate the idea of firing a low performer and cheaper context switching

    In this episode, Dave and Jamison answer these questions: Hi Dave & Jamison, Long time listener, first time google-form filler outer! I work in a hybrid role as a lead developer and manager of a small team (less than 5). I’m new to management and most of ny experience so far has been with smart, motivated engineers. . . UNTIL! My new recruit is driving me crazy, they are clearly very capable, but just do not do the work. They are frequently late for work, frequently sign off early, and constantly evasive when I ask for updates. I have spoken to them about these issues a bunch, and everytime they are apologetic and say they “have some personal issues but are working on it” - and nothing changes. Urgh! I am pretty sure I will have to fire them, but I feel terrible about it! I know I can’t keep them on and pay them to do nothing, but what’s the best way to let somebody go? How do I break the news to the rest of the team? How do I avoid feeling bad for the rest of my life? Yours guiltily, Anon A listener named “erm what the sigma” asks, Do you have any advice on how to reduce the ramp-up time when context switching? I’ve always felt like context switching comes at a high cost for me—it just takes so long for me to mentally shift between tasks. This wasn’t much of a problem before, but I’ve recently become a tech lead and now my calendar is cluttered with meetings (why did I ask for this again??). I’m struggling to complete my coding stories because just as I hit my stride, I get pinged by someone on my team to help them or have to jump into yet another meeting. pls send help

    38分

  8. 8月11日

    Episode 473: Mental health support and overcoming FOMO of taking a break from work

    In this episode, Dave and Jamison answer these questions: Hi Jamison and Dave! I am not a developer, but my question is hopefully transferable. I sit in between lawyers and developers. I advise on technology that can be applied to legal processes and I support our teams in using a range of platforms and AI tools to be more efficient across their work. I have ADHD (late diagnosis at 22) and often have trouble with executive function, remembering details, progressing large projects with no deadlines, and remembering verbal instructions. Have either of you ever had a neurodivergent person on your team? If so, how did you support them? What environment helped them to work best? Also, what frustrations did you have and how could they have mitigated them? Any help would be appreciated to help me avoid driving my manager insane (I live in constant fear that one day she will snap and I’ll be fired even multiple years in). 😂 Hi Dave and Jamison, you’ve made my runs very enjoyable over the last years, thank you so much for that - even though I doubt that laughing out all the time is great for my performance. I’ve been in web development for 7 years now and a Lead Fullstack Engineer at a consulting firm. Being a “lead” currently only means that my team mates seek my opinion and guidance on topics, without me having any increased responsibility. In September, I’ll move countries (Europe to Australia) and will be on parental leave until mid ‘26 when I’ll have to look for a new job down under. I feel quite stressed by recent developments (AI), already have the feeling of not being able to keep up with all the new things (ask my 300 open tabs of articles I want to read), and fear that I could loose touch in my time off. How can I deal with this FOMO? And which topics would you look into in the upcoming months if you were in my place? Show Notes https://blog.jsbarretto.com/post/software-is-joy https://medium.com/@djsmith42/the-3-highest-roi-technical-skills-for-software-developers-21b412d79aff

    36分
すべて見る（481）

評価とレビュー

5
5段階評価中
6件の評価

番組について

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.

情報

  • クリエイター
    Jamison Dance and Dave Smith
  • 配信期間
    16年 - 25年
  • エピソード
    481
  • 制限指定
    不適切な内容を含まない
  • Copyright
    © 2016 Jamison Dance and Dave Smith
  • 番組のWebサイト
    Soft Skills Engineering

その他のおすすめ