In this episode, Dave and Jamison answer these questions:

1. How do I quit my first job if I’m working with a manager I love?

   I started my first full-time job about two years ago and I’m starting to think about looking for a new job, both because I am ready for new challenges and I’m ready to move to a new city.

   I have a great working relationship with my boss, so a part of me wants to tell her about my interest in finding a new job, both so that I could use her for a reference and also so that I can be honest with her about my intentions. She’s been a great boss and mentor to me, so there’s a part of me that doesn’t want to jeopardize our working relationship. But another part of me feels like I might be jeopardizing my presence in my current office if I make it clear that I am looking to move on, especially if my job hunt doesn’t go as smoothly as I hope.

2. How do you deal effectively with rapidly increasing work responsibilities?

   My technical lead was recently promoted to management. Being both ambitious and the only Sr. Engineer without retirement plans in the next 4 months, I immediately stepped into the power vacuum and inverted a binary tree faster than all my coworkers to establish my position as new tech lead. After a few months the other senior engineer on my team retired, and I’ve ended up holding the bag for my new job responsibilities, my old responsibilities as a Sr. Engineer, AND the departed Sr. Engineer’s responsibilities.

   I told my manager how much was on my plate and that I was afraid my work output would suffer, and her response was to throw money hand over fist at me and promise to backfill both Senior positions within the next 12 months.

   How do I get through the next 18 months without losing all my hair? Are there any strategies to make sure the team doesn’t go up in flames when I forget about a key deadline? Or at least position myself so that nobody can tell it is my fault until I can make a subtle getaway in the brand new Ferrari I’m going to buy?

In this episode, Dave and Jamison answer these questions:

1. Hey guys, I’ve graduated with a CS degree 8 years ago, but due to circumstances I accepted a QA job because I wasn’t getting any other offers. Well 8 years later, I’m still stuck in QA and would love to move into development. I tried transferring within companies and applying to developer jobs, but the QA brand is holding me back. Any advice on how I can become a developer when I’m pigeon-holed in QA?

2. Hi folks! I need your wisdom! Please help. TLDR: Senior as a Programmer, Junior as a Mobile developer.

   When I first came to my job as an intern, my manager asked me what I wanted to do more - backend stuff, testing, or mobile development. I went randomly and chose the latter. It became my profile and I’ve grown to really like it. Over the years, life has thrown me back and forth, I’ve been on multiple different projects not related to mobile, so now I can do… everything? Or rather, nothing. I know a little bit about .NET, a little about web development, writing Visual Studio extensions, IoT, machine learning, Unity game dev.. This is good because I can now quickly learn new things, know a lot of tricky stuff, know how to communicate with customers. I have a decent salary and good feedback.

   But the huge downside to that is that I stayed exactly at the same level of mobile development as I was 3 years ago. I know basic stuff, a little bit of advanced stuff, but I have zero experience in all the ““hot”” things like RxJava, Dagger, Kotlin.

   All the job vacancies I’ve seen require a strong knowledge of something particular: be it Android or iOS development, backend or frontend. I’m suffering from a huge imposter syndrom - yes, I have all the ““good”” programmer qualities, I’m smart, but I have no advanced or even medium knowledge in anything. What can you advise me?

   Huge thanks and… love the show! ❤

In this episode, Dave and Jamison answer these questions:

1. Is it weird to have 1-1s but not with my ‘manager’?

   Management is planning to start holding ‘1-1s’ every 6-8 weeks for the development team.

   The purpose of these 1-1s: ~ ‘So you can talk about non-technical things, any issues with the team or things that are making you unhappy.’ But these 1-1s be with someone who is nominally ‘HR’, not our manager. Since it’s a tiny company, their responsibilities cover things like accounting and sales support.

   This person doesn’t have any people management or software product development experience, nor any experience in our product domain, and won’t really be our ‘manager’ going forward.

   Maybe I should just 🎶 quit my job 🎶 🕺. Then I’ll have new and unfamiliar problems to worry about 😅

2. Hello Jamison and Dave, I have a question on career progression, tech skills and moving into a new role.

   I’m a career switcher who has spent the last four years studying to move into a developer role.

   Over the last year I’ve been working on a technical project that has been delivered on time, under budget and ahead of schedule, a huge win for me and the team. However, now that it’s done my manager’s manager is looking at how the team is structured and who we need to hire.

   He has come to me and my manager to ask if I would like to move in to more of a Project Manager / Business Analyst role as I have done such a good job of the project roll out this year.

   I’m good at that kind of work, I do get a kick out of it, but if I don’t push forward to move into a developer role have I wasted the last four years retraining? Should I take the role and continue to push to be a full time developer on the team, or accept my fate but use the skills I’ve gained to be a better BA?