In this episode, Dave and Jamison answer these questions:

1. I was on a meeting with a team generally regarded to be pretty annoying to deal with and not particularly useful. The meeting was pretty annoying and not particularly useful. I audibly said to myself after leaving “holy crap what a waste of time.” Turns out I hadn’t left and may not have been muted (?) but I’m really not sure. I left immediately without checking due to cringe overload, so I have no way of knowing.

   How do I even go about this? I have to meet with this team regularly. My spirit has left my body, this question was typed by the husk that remained.

2. I am almost 2 years into my software development career. A few months ago, I was moved to a team where I was the only frontend developer. My team responsible for maintaining a large, legacy angular project and building a new internal in React tool to support the ML engineers at our organization. Our organization hired some contractors to help with building the new tool, all of which have the same or less dev experience as me.

   Our project manager is not engaged in our project. He is on multiple teams. I have to communicate with our customer, gather requirements, create user stories, and QA the contractors’ work. This is not the type of work I am particularly good at or enjoy. This is on top of me being the de-facto frontend tech lead. I am STRUGGLING to keep up. I can only do a little bit of work on our project each iteration and doing required maintenance of the legacy application has become very difficult to do because of how little attention I am able to give it.

   I don’t want to do all the other stuff, I just want to write code. What should I do?

In this episode, Dave and Jamison answer these questions:

1. I’m a long time listener to the podcast. Thanks for reading and answering my question!

   I have over 20+ yrs experience as a manual QA and 6+ yrs experience as a SDET. I’m in a new role as a hybrid manual QA / SDET for a company that hasn’t had QA for a few years. After a couple of months a new hire was added to support a new project in non-development or QA tasks. While waiting for the launch of the new project, senior leadership decided to have this new hire to help me with QA. They have no experience in QA or coding. I spent a considerable amount of time training them, and found it difficult.

   After a few months my manager told me the hire will transition to lead QA. They will NOT be my supervisor or manager. I will be answering directly to the manager as before. I feel sidelined since I didn’t get hired on as a Sr. or Lead role. I’ve already been left out of numerous meetings catered to team leads only.

   The new hire is very vocal in meetings. They repeat my ideas as their own, and speak for me when I don’t agree. It’s exhausting to hold back ideas from the new hire or correct them and add context to the rest of the team when I disagree.

   I’m worried I’m training this new QA lead to be my replacement. What are your thoughts? I feel like the company culture is chaotic for the long term. Any thoughts what I should do in the short term and long term?

2. Hi Dave and Jamison (as a unit would you answer to Davison?). Long time listener, first time caller.

   I recently joined a data-engineering team at chill 90s multi-national tech company. My boss and I are based in the UK, and two more junior engineers who do the bulk of the IC work are based in India. These two engineers seem to work hard, have far more domain knowledge and technical ability than me, and generally seem to do most of the work. There’s also a senior engineer who’s kind of absent.

   My boss is a ‘red personality’ who’s been at the org for at least a decade, who doesn’t seem as close to the technical detail. He cares about the destination and wants to get there yesterday, but discussions about ‘ways of working’ or the specifics of achieving the output seem to bore him. He characterizes such talk as risk-aversion.

   I’m shocked by some of the technical details. Tooling chosen specifically to bypass version control, editing Jupyter Notebooks to deploy changes to ‘production’, dashboards that seem to have totally wrong data, etc.

   It seems like they will do the minimum required to make things ‘work’ and then move on. Scalability or making things interpret-able for others just doesn’t seem to weigh on their mind. It’s then me as the new-joiner navigating their hacky code who inevitably wanders into all the pitfalls and gotchas.

   I’ve tried to advocate for better practices and lead by example. They nod along, but ultimately seem resistant to change. I need their help and experience with the codebase, but I also have this creeping sense that their working style is too sloppy and unprofessional. They don’t report to me, and our mutual boss seems happy with the work. I feel a bit like the guy in Twilight Zone: I can see a gremlin wrecking the plane, but nobody else can see it, and my attempts to address the situation just seem a bit hysterical.

   What’s worse, my gentle attempts at flagging the issues with my boss haven’t gone down well. In my first performance review my boss mentioned something about a ‘us versus them attitude’ and ‘assuming good intent’.

   What do you make of this situation? Am I the a-hole? Have you faced this sort of thing in the past? Is it time to consider old-reliable? Is 4 months too soon to quit a job?

In this episode, Dave and Jamison answer these questions:

1. Hi Dave and Jamison,

   Long-time listener, first-time question asker. Thank you both for the wisdom, perspective, and jokes you bring to the podcast.

   I recently received an inheritance of around $500,000. It’s not “quit your job and buy a yacht” money, but it is enough to reshape my life. I’m in my late 30s, currently working in a senior engineering role. I’ve had a solid run in the world of code, but I’m ready to walk away from it, zero regrets, just done. What’s pulling me now is UX and product design: more creative, human-centered, systems-aware work.

   I’ve applied for a one year master’s program in UX design, starting in 2026. I’m planning a sabbatical before that to travel, reset, and explore - think trains across Canada, a design conference in Vienna, a food tour in Greece. I’m also investing in short courses and portfolio work during that time.

   Financially, I’ve been careful: I paid off my mortgage, invested part of the inheritance, and set up a buffer. So I’m not winging it… but I am stepping away from a six-figure salary, a career my friends and family have supported me to build, and am will have no income for the next 18 months, and that’s a little scary. I want to use this opportunity well, not just coast, or panic-spend, or accidentally put myself in a worse position five years from now.

   How would you approach this kind of mid-career pivot with a windfall cushion? Any mental models, risk assessments, or “soft skills” wisdom to help me stay brave and smart?

   Thanks again for everything you put out into the world.

2. Hi Soft Skills Engineering Team,

   I’m the oldest person on my team (by a respectable margin), and I’ve been taking great delight in gently baffling my younger colleagues with expressions like “I’ll get that done in two ticks,” “give me a bell if you need help,” and “stay on the line after stand-up” (even though we’re on Teams, not a landline).

   It has become a bit of a sport for me to see how many retro, obscure, or regionally-specific phrases I can sneak into our chats and meetings before someone finally asks, “What are you even saying?”

   My question is: What other delightfully old-school and vaguely professional expressions can I deploy to maintain my status as the team’s resident linguistic cryptid?

   Thanks for all the great advice you give, and for validating my mission to keep corporate life interesting!

   Warmest regards, Resident Old Person