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. Is it common for developers to take an interview without real interest in a job?

   Is it common for a company to reject a candidate because they think candidate is not interested in a job?

   Recently I had an interview and I was rejected even though I though it went really well. From internal channels in that company I learned that the interviewer thought I wasn’t really searching for a new job and was just doing interviews for fun or to improve my skills. That was really frustrating. And also, well, flattering. But still, I don’t understand what signals I may have given. I asked questions about the company, processes, etc. I prepared really well. And I asked for a salary that’s quite significant for our market.

   The only reason I see is that I always worked remotely and this is position in an office.

   By the way, LOVE your show!

2. What happens when a wave of engineers leaves your company?

   I work for a startup that went through a brutal round of layoffs, before stabilizing. We’re building the engineering team back up, but the core team members that built our platform are gone.

   How do we approach maintaining things, adding new things, technology decisions, etc?

In this episode, Dave and Jamison answer these questions:

1. Hello Jamison and Dave. 💕 your show! 👏

   I have been a C# dev for 7 years. Last year, I learn Erlang. I fell in love with functional programming. After that I learned Elm and oh boy… I had never dreamed a compiler/computer could do so much work for me, preventing so many mistakes that would otherwise require an unholy number of “unit tests”.

   The thing is I can no longer find satisfaction with any job. I love to write software, but at some point I became almost dogmatic. I abhor more and more the discipline it takes, in certain languages, to make my code be as pure and testable as in an FP language.

   I had to do so much un-learning, that now I feel that I am refusing to un-un-learn all these different ideas and paradigms and just go back to making the tests happy.

   I seek your humorous words of wisdom on how to find contentment with my job again, without looking at a language and dreading it.

2. I have a co-worker, who is pretty incompetent technically. Over the past few years that I’ve been here, he has proved time and again that he is incapable of learning and really grasping how things work. He is able to accomplish basic feature work, but not capable of making good architecture decisions, or why a given framework should be chosen, or how to solve harder problems (I’m not sure how to describe this. But for example, how to build a resilient API client).

   However this person is great at creating slides, and presentations, and JIRAs, so I think management thinks they are ok at their job.

   He’s also a nice guy. I’m not sure how to say, hey you suck at your job. Which is pretty harsh. Or to suggest to someone that he should be replaced.