app_store_button

google_play_button

is Device Banner Block 894x1036

Stígðu inn í heim af óteljandi sögum

Hlustaðu og lestu

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.

Soft Skills Engineering

In this episode, Dave and Jamison answer these questions:

 1. 

How would you handle a situation where a team forms a negative opinion about you from day one — without any clear reason and without ever giving you a real chance to prove yourself?
 2. 

Even when you contribute technically, your suggestions are ignored… until someone else repeats the same thing and suddenly it’s considered valid.
 3. 

Is it possible to stay in that kind of environment without becoming bitter or burned out?
 4. 

Can you keep contributing professionally — or is it healthier to just walk away?
 5. 

 6. 

You guys are awesome. Jamison, I interviewed with you and it was lots of fun and productive. Which is really rad.
 7. 

Now… I just landed a 12-month contract in big tech role. It’s perfectly aligned with my long-term career goals. My current fintech FTE is perfectly opposed to my long-term career goals.
 8. 

The question — how unethical / despicable would it be to start one week of PTO at my FTE on the same day as Day One at my contract role so that I can onboard without distractions and then put in my resignation upon returning to my FTE? What about two, three, or four weeks of PTO?
 9. 

Also… are two-week notices still the default still in 2025?
 10. 

Also also… I promise I’m not AI — I’ve been using em dashes since the 20th century.
 11.

Episode 483: My team hated me from day one and should I stack PTO before my resignation

In this episode, Dave and Jamison answer these questions:

 1. 

After a year of trying, I recently got promoted to staff engineer!
 2. 

It’s great to receive recognition for my work, but i’m not actually very happy, because I only got a 4% raise! I spoke with a former coworker about how much a staff engineer in my role should expect, and he said that he would be insulted by less than . My comp is now slightly below !
 3. 

In addition to this, times are tough for the business, so it seems unlikely that we’ll get annual bonuses, meaning I likely won’t even get to appreciate the larger target staff bonus! What a bummer!
 4. 

How should I approach this? A year and a half ago after getting a below inflation raise, I was told I was at the top of my level’s pay band and would need to get promoted if I wanted to go much higher. Now that I’ve gotten promoted, it seems like that wasn’t true! I should be grateful that I still have a job and got promoted and got any increase, but I feel like I’m being short changed! How can I talk to my manager to see about getting more money?
 5. 

 6. 

My company does not address complaints. Here are two examples.
 7. 

On my first day, the lead engineer told me not to participate in the project. He was impossible to work with: He’d hold up PR’s for 3 months because of linting and prettier rules. Eventually, I figured out he was exceptionally insecure and wanted no feedback or anyone to expose his technical weaknesses. I conflicted with him a lot and got shuffled to another department.
 8. 

My 2nd example comes from a trainee. I helped him out everyday after standup for 30 minutes. How he passed his interview, I don’t know. He didn’t know what a semicolon was after a 4 years bachelor in computer science and 6 months of being a trainee. I complained to a friend at work who had, I didn’t know, interviewed the trainee. My friend was surprised, and so we hopped on a call with the trainee who didn’t recognize my friend. After snooping around on social media, we found the guy who had done the interview, the trainee’s brother. I told HR & my department head. Nothing happened.
 9. 

Here’s the question: Getting kicked out of a department ruined my confidence. I have a safe, secure job where there’s no pressure. But my firm doesn’t address complaints properly. Time and time again, people will complain about the linting/prettier guy or other issues like the trainee and nothing is done. Should I leave? I work on a greenfield project here. Switching to a (likely) legacy codebase I didn’t build and dealing with higher pay/expectations is very daunting.
 10.

Episode 482: I got a promotion, but a tiny raise and an imposter interviewed for my team

In this episode, Dave and Jamison answer these questions:

 1. 

Hi Dave and Jamison,
 2. 

After fleeing a sinking ship of a startup, I became a solo developer at a medium sized college. This role has really allowed me to expand and grow in ways that I haven’t imagined, but I have encountered an interesting issue I didn’t have in the startup world: there isn’t much to do.
 3. 

At my one year mark, I was promoted into a management position, but with no direct report. I will soon have an employee under me doing data integrations. My manager has been reluctant to give me data integrations work despite knowing that I want to understand what my employee will be working with.
 4. 

I’ve found some of my own projects, but I’ve completed them all. I’m getting bored. I’m a competent developer, learn fast, and get things done quickly. Recently I’ve been planning an upgrade to some of our legacy code, but it will take probably a year or more to complete.
 5. 

Some former colleagues reached out about working with them for a substantial pay bump, but I don’t like the idea of leaving after just over a year and a half. Do I keep riding it out here, or is it time to start looking else where?
 6. 

Thank you both for this wonderful podcast. Its a joy to listen to on my walks. I’m sure I get stared at when I try to hide a laugh or grin from the amazing list of Patron names and your commentary.
 7. 

 8. 

I was recently terminated a few months before my 1 year vesting cliff as an IC2 for being days (not weeks) late on 3 or 4 stories. The late ones were defined incorrectly by management, or were for paying technical debt created by senior engineers, and my manager knew this. I had no IC2 or IC1 peers on my team for comparison. My performance review for the first half of 2025 was not released to me, I was fired when I would have seen it. This means the only reasoning that management has shared with me was my late work. In 1 on 1s before, my lateness has been something my manager has mentioned, but never a warning of termination (or a “pip” as some call it) and no indication that it’s anything more than an area to improve. The org has made poor decisions that left them tight on funds, and I feel the most financially responsible thing for them to do was fire me rather than give me a warning which would let me hit my cliff or lay me off where they’d give more on my way out.
 9. 

Had I been pipped or laid off, I would not be asking about this. Should I go with the confusing justification that my boss was truthful in his attribution of my firing without warning to my lateness (and can you help me understand why that’s professionally justified)? Should I go with the disheartening approach and brainstorm other shortcomings that would better justify an unwarned firing, possibly spurring professional growth or a career change? Or should I say I got instafired because of penny pinching and opaque management?
 10.

Episode 481: I'm bored and will I ever find out why I was fired?

In this episode, Dave and Jamison answer these questions:

 1. 

(follow-up from question 449)
 2. 

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.
 3. 

I assume he is also a long time listener of this podcast and took the age old “leave your job” advice. Kudos.
 4. 

(question below)
 5. 

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.”
 6. 

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?
 7. 

 8. 

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!
 9.

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:

 1. 

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.
 2. 

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.
 3. 

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.
 4. 

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?
 5. 

 6. 

Listener k pop demon hunters asks,
 7. 

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?
 8. 

Thanks for the great show. It’s making my commute more enjoyable. Keep it up!
 9.

Episode 479: Contractors to the rescue and dinged for delay

In this episode, Dave and Jamison answer these questions:

 1. 

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?
 2. 

 3. 

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.
 4. 

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.
 5. 

The routine is always the same:
 6. 

 1. He asks the engineering team how to achieve some goal (always involving an LLM).

 2. We give a sensible answer, weighing complexity, cost, feasibility.

 3. He comes back with a massive pasted transcript: “here’s what ChatGPT thinks.”

 4. We pick out what’s actually useful, quietly bin the nonsense.

 5. He takes our response, shoves it straight back into ChatGPT, and returns with another transcript: “here’s what ChatGPT thinks.”

 7. 

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.
 8. 

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?
 9.

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

In this episode, Dave and Jamison answer these questions:

 1. 

Hey guys,
 2. 

I have been working for four months at my job and I already don’t like it.
 3. 

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.
 4. 

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.
 5. 

 6. 

Listener Ghani asks,
 7. 

“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.
 8. 

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
 9. 

my impressions were
 10. 

 • 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)

 11. 

I really want to look for where we can have a safe exchange of information. How can I do this?
 12.

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

In this episode, Dave and Jamison answer these questions:

 1. 

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?
 2. 

 3. 

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?
 4.

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

In this episode, Dave and Jamison answer these questions:

 1. 

Hi!
 2. 

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.
 3. 

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)?
 4. 

 5. 

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!
 6.

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

In this episode, Dave and Jamison answer these questions:

 1. 

Hi Dave & Jamison,
 2. 

Long time listener, first time google-form filler outer!
 3. 

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. . .
 4. 

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!
 5. 

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?
 6. 

Yours guiltily,
 7. 

Anon
 8. 

 9. 

A listener named “erm what the sigma” asks,
 10. 

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
 11.

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

This week Jamison and Dave answer these questions:

 1. We’ve re-written the project I’m on 10 times without launching. What should I do?

 2. I worked hard to hit a deadline, only to find out the deadline was moved. How do I avoid this in the future?

We talked a bit about the value of deadlines way back in episode nine if you want to hear some positive things about deadlines.

Episode 78: Endless Rewrites and Fake Deadlines

Hlustaðu og lestu

Other podcasts you might like ...