In this episode, Dave and Jamison answer these questions:

1. I stayed too long at my first company and now my career is ruined?

   Hi both, long time listener. (Since I graduated university 4 years ago actually and felt I could never find a job but listening to you guys made me feel not like such an outcast in our field.)

   I graduated in 2022. Didn’t really apply around much and almost immediately accepted the full time offer from the company I did my internship with during my degree. And fast forward to middle of 2026… I am still here.

   I’ve long stopped growing as an engineer and have actually been stuck on a simple CLI tool for almost 4 years now with little to no cloud/backend/etcetera experience to show in my 5 year career. I don’t feel I am desirable in the job market at all due to this and waited way too long to look for a job because I was comfortable and happy. I feel paralyzed (no need to put on your space therapist hats BUT some career advice would be wonderful!)

   (Also did I mention I am in Canada and want to move to Europe and live the rest of my life there but visa sponsorship with my level of experience is impossible? Maybe that’ll be for my next question…)

   Thanks for all you do, cheers!

2. I have a non-CS engineering degree, and am looking to transition into Software Engineering. I have the option of pursuing a degree with Tuition Reimbursement from my job, but am in a bit of a strange situation deciding which degree. Basically, I’ve figured that with my current Engineering background I could pursue either a second Bachelor’s degree through Universities offering a “Post-Baccalaureate” program in Computer Science, or a Master’s degree, with maybe only a slightly longer program to get the Master’s as opposed to the Bachelor’s. Otherwise the total length/cost of the programs would be roughly the same.

   I have heard though that it might not be a great idea to go into a Master’s program unless you know what specifically you want to study.

   I am curious what you think would be more “hire-able” between the two options for someone pursuing the career change into Software Engineering?

In this episode, Dave and Jamison answer these questions:

1. Dwill Ainghell asks,

   During the golden era of software development, it was commonly stated that you should always negotiate job offers. The argument was that the company has invested significant time and resources into you as a candidate and there is always some wiggle room for negotiations. A popular article / podcast by Patrick McKenzie likened it to doing something slightly uncomfortable like “reciting poetry while simultaneously standing on one foot” with almost no downside. (https://www.complexsystemspodcast.com/episodes/how-to-negotiate-your-salary-package/)

   Does this still hold true in today’s environment? I’m a SWE with 10 years of experience and I’ve been unemployed for close to a year. I’m expecting an offer from a large company and I fear that I will look like a fool trying to negotiate in my current position and the current job market dynamics. Even worse, I fear that they might retract the offer and give it to someone else. That being said, I don’t want to leave money on the table.

   What’s the correct course of action in today’s environment?

2. Listener Stu says,

   In episode 500, you said something to the effect of “working hard and doing a great job with the work you’ve been assigned is not the promotion track”. I’d love to hear you discuss what it does take to get promoted and how to do that.

   In my job, we have a jira queue and engineers are tasked with taking from the top of the queue and executing work. There’s also an expectation to lead pre-defined projects (define the scope, write the tickets, and shepherd it along).

   All of these projects have deadlines, so how do you recommend people get the defined work done, lead projects, and still find time to do whatever it is to get promoted?

   Why is doing an excellent job not enough?

In this episode, Dave and Jamison answer these questions:

1. Hey Dave & Jamison,

   Long time listener. Love the podcast.

   I recently rejoined a remote team that I worked with in the past. I was super stoked to rejoin this team because they were collectively one of the most competent and technically excellent teams I’ve ever worked with. And they’re all genuinely nice people as well.

   I left the team before AI coding had really caught on, but coming back to the team has been a huge shock to me. Almost everyone now exclusively writes code with AI. PR descriptions are all AI generated, and code review has become copy-pasting AI-generated comments into GitHub.

   Being a remote team it was already hard to connect, but now it feels like almost all interactions are their AI assistant talking to my AI assistant.

   I’m not anti-AI, and I get that writing code with AI can be much quicker. But I’m struggling with the loss of what made the team feel good to work on, specifically the craftsmanship, level of engagement, and the learning from eachother. The product itself is still high quality (even if the codebase is less-so), but the process itself is a lot less enjoyable now.

   I don’t want to be the person who shows up after being away and immediately makes it everyone else’s problem that I miss the old way of doing things. But I’m having doubts if I want to be a part of this team.

   Is this just what software engineering looks like in remote organisations now? And should I expect most teams are now operating like this?

2. Hi Jamison and Dave,

   Love your podcast.

   I was recently hired as a mid-level full-stack developer with the promise of leading a new squad. On day one, I discovered management scrapped the squad idea and promoted an existing developer to sole lead instead.

   The team consists of this new lead, two 20-year VB6 veterans, and me. The codebase is lawless: direct DB access, fat controllers, 1-2K+ LOC classes everywhere (copy/pasted boilerplate) and severe Broken Access Control (OWASP #1) where authenticated users can extract anyone’s PII (full name, home address, phone number) via a simple email query string.

   My coworkers rely heavily on generative AI but do not review the output. They constantly commit “AI slop” that barely functions and introduces endless bugs. I used to clean it up, but I recently realized they care so little about the codebase that no one even notices if I stop. Add in a “Senior Product Manager” whose entire UX background is a three-month internship, who invents customer requirements to defend her inconsistent designs.

   I am already applying elsewhere.

   My questions:

   How do you handle a bait-and-switch of this magnitude?

   When the team cares so little that no one notices if you stop cleaning up their AI-generated bugs, how do you stay sane and professionally sharp while riding out the clock?

Show Notes

• https://tombedor.dev/human-attention-and-human-effort/