Episode's summary
In this episode, Dave and Jamison answer these questions: Dave and Jamison, long time listener first time caller. I appreciate everything you do, I look forward to my Monday morning commute because of this podcast. I’ve been a software developer for about 4 years. I’m a career changer and graduated from a boot camp. I was fortunate enough to earn a junior developer position at a non software company and have been promoted during my tenure. I work on a small team and enjoy what I do and the level of impact I have. I am one of the most senior developers. My only concern is that I do not receive direct mentorship from more experienced developers. Am I limiting my future prospects by not job hopping? When is the right time to leave a company and seek new opportunities? Hello Mr. 💃 and Mr. Smith. I’ve been working in software ~6 years. In the same company (don’t judge). And about a year ago I advanced in the position of a team lead of 4 developers. I would actually like to attribute this advancement, at least…
In this episode, Dave and Jamison answer these questions: Dave and Jamison, long time listener first time caller. I appreciate everything you do, I look forward to my Monday morning commute because of this podcast. I’ve been a software developer for about 4 years. I’m a career changer and graduated from a boot camp. I was fortunate enough to earn a junior developer position at a non software company and have been promoted during my tenure. I work on a small team and enjoy what I do and the level of impact I have. I am one of the most senior developers. My only concern is that I do not receive direct mentorship from more experienced developers. Am I limiting my future prospects by not job hopping? When is the right time to leave a company and seek new opportunities? Hello Mr. 💃 and Mr. Smith. I’ve been working in software ~6 years. In the same company (don’t judge). And about a year ago I advanced in the position of a team lead of 4 developers. I would actually like to attribute this advancement, at least…
Episodes
Episode 536: Mentoring and how to help my team not lose their soul to AI?
ListenedIn this episode, Dave and Jamison answer these questions: Dave and Jamison, long time listener first time caller. I appreciate everything you do, I look forward to my Monday morning commute because of this podcast. I’ve been a software developer for about 4 years. I’m a career changer and graduated from a boot camp. I was fortunate enough to earn a junior developer position at a non software company and have been promoted during my tenure. I work on a small team and enjoy what I do and the level of impact I have. I am one of the most senior developers. My only concern is that I do not receive direct mentorship from more experienced developers. Am I limiting my future prospects by not job hopping? When is the right time to leave a company and seek new opportunities? Hello Mr. 💃 and Mr. Smith. I’ve been working in software ~6 years. In the same company (don’t judge). And about a year ago I advanced in the position of a team lead of 4 developers. I would actually like to attribute this advancement, at least…
Episode 535: Manager externalities and should I fight stupid processes
ListenedIn this episode, Dave and Jamison answer these questions: Listener Random Listener asks, You guys talk a lot about externalities, which helped me understand a lot about how my manager works. He wants to do things fast, but he does not follow good and standardized processes, even the ones he tries to push onto us. This adds a lot of work for us because now his mess becomes our mess. How can I give him this feedback in way he will both understand and not feel resentment? Thanks Hello. I am individual contributor and have been with this team for 2 years. About a year ago a manager and a lead joined the team to fill in the growing positions. They came in with their preferences for code design, architecture, and ideologies. But they were all different from how we worked before. Their ways are not bad, but they add unnecessary complexities, taking away energy from just doing my pick-up - code - ship way. I shared my concerns, but they never get accepted as they just want to exercise their manager and lead powers.…
Episode 534: I'm so bad at my job and I've inherited a huge slop pile
ListenedIn this episode, Dave and Jamison answer these questions: Hi Soft Skills Engineering, I’m a senior software engineer with over 20 years of experience. I’m hoping you can help with with a problem where I’m dumb, weird and bad at my job! There is a recurring problem where, despite all my experience and graybearding, despite my big words, I sometimes just miss very important details, and ways that are very consequential and cause time and feature gaps. Sometimes I make a faulty assumption and gloss over initial errors, and later I get big errors that require big fixes. For example, sometimes I just miss random lines from a product spec or whole parts of the UI, like a blind spot, or like a Mandela situation where I could’ve sworn it was different where I read it. Sometimes, I read the docs on some library but didn’t really *read* the docs and missed the important line that I needed before things get broken. It’s a soft skill, sorta, because it’s about how I go about my work, and I don’t know what I can do about…
Episode 533: I'm drowning in AI slop from lazy coworkers
ListenedIn this episode, Dave and Jamison answer these questions: Hey Dave and Jamison. I don’t know what to do with the amount of the AI slop I have to review and I’m getting close to burnout. I have a lot of context on my project, so my colleagues see me as a point of reference. Additionally, at a past job, I was a tech lead and could easily cover for TL if I wanted to (which I don’t) and I feel like the TL of my project and some of my teammates are taking advantage of this. Every day I receive a lot of low quality documents to review. For example, our TL creates sloppy project planning documents and tickets and sends them to me for comments. Since they contain so many errors, sometimes including obvious security or data compatibility issues, or just text that is unrelated to the project, I end up basically rewriting everything. The same thing happens with code reviews. Some code is obviously AI-generated slop with lots of duplication and errors, that in many cases misses acceptance criteria or has doc strings…
Episode 532: My new company is an absolute mess and should I get an English-speaking job as a Japanese engineer?
ListenedIn this episode, Dave and Jamison answer these questions: Hi Dave and Jamison, I’ve been a Java backend dev for over 10 years. After getting laid off from a job I loved, I spent 3 tough months job hunting. I eventually landed a full-stack role at a non-tech company where I am the entire front-end department. The team is a mess: A CTO who hasn’t coded in years and calls me directly to assign tasks, all labeled “highest priority.” When I asked the CTO and CEO if we had QA, they literally laughed at me. Prod releases are “tested” by the CTO before telling me to push immediately. I’m at a crossroads: Stick it out for 6–12 months to gain AI experience, then quit? Try to move into management, and rebuild this mess into a functioning engineering organization. What should I do? Hey, Dave and Jamison. I’m a non-native Japanese speaker working in Tokyo with about 6 years of experience in backend(3 years in Tokyo) and haven’t used English in work. I started listening to this podcast for learning English. And I soon…