In this episode, Dave and Jamison answer these questions:

1. What advice would you give for working with an ineffective leader whose input is crucial to your work? I’m a senior developer for a mid-sized non-tech company with probably 60-80 devs, and in the past year I’ve been working more with a VP of software who seems to still be involved in code details, getting pulled in to production issues, in-person code reviews, etc.

   He’s a nice guy, but he seems like he’s being pulled in too many directions at once. When he schedules a meeting, there’s a 50% chance it happens on that day and time, and when we do have meetings, if we bring up questions and high level issues we need feedback on he’s quick to “take ownership” and say he’ll do X and Y. Inevitably, X and Y slip down the priority list because production issues and who knows what else, and we’re stuck waiting weeks on end for something that if he’d just delegated the work to someone else, we’d have long since moved on. But we still need his input to shape our work. How can we as lower-level developers (with a manager who isn’t involved in this project at all) help mitigate these delays?

2. I’ve recently accepted a new position after spending more than three years at my first job out of college. Currently, I’m a Senior Engineer at a large, corporate-like company (300+ people), but my new role will be at a much smaller startup (20-30 people).

   I’m excited about the change but also a bit nervous, as I know startups can be fast-paced, and I’ll need to get up to speed quickly.

   What advice do you have for setting myself up for success in this new role—both before I start and after I begin? I have a couple of weeks before my start date and want to use that time to prepare effectively.

In this episode, Dave and Jamison answer these questions:

1. I am a first time caller and full time listener of your show.

   I was released from prison a year ago and I coded for 18 years straight on all sorts of stacks as part of my job requirements in the pen. Imagine the irony when I discovered what codepen was.

   A dev told me about an opening for full remote/full stack web dev at their company. I’ve used the tech stack before but I have a non-traditional background to say the least. I’m not worried about being qualified but I have never worked in a team and I have always been responsible for production.

   I work for a large retailer in a non-coding role. I’m also doing some freelancing on upwork/fiverr, but the pay is low and the jobs are not fulfilling. I was self-employed before I was incarcerated and I know how to beat the pavement and get small time work, but this is an opportunity to work at a real software house. I don’t even care if it’s a feature factory, I just have loved coding since I was 14.

   What do I do? I am confident in my skills and ability to deliver under pressure (in a place that has pressures you can’t imagine). I have a cover letter, but a bad resume and no open source projects from this millennium. I do have a reference - a Captain I worked for said he was willing. However, the opportunity was unexpected and I have not prepared anything.

   The dev who brought me the offer was a casual friend in IRC and he told me that my resume was mentioned in some meeting. I know you have suggested in previous shows that having someone get your foot in the door is the best way but I really think that feels gross to me.

   Anyways, longtime listener of your show and first time caller. In fact, when I was in prison, a few years before I was released we finally got tablets with an incredibly limited amount of content. Your show was one of a few on coding but I really enjoy your take on the soft skills because even though I worked in a non-traditional environment, teamwork was always the focus and I listened to everything from square one (took me a long time to get there).

   So thank you for your podcast you don’t know how many times I could sit in my cell listening to your show and disappear from my cage.

   Sincerely, Names have been change to protect the guilty

2. Second time caller from NYC! I previously wrote in as an 18-year-old CS graduate (Episode 332).

   I’ve focused intensely on work for the past 4 years, consistently working 60+ hours per week.

   I always assumed that this approach to life would eventually bear fruit, but a couple months into turning 20, I’m realizing that I haven’t really done anything memorable besides work (which is a scary realization at 20).

   While I like working hard and want to ensure the success of the company I work for, I also want to feel like I am living. How have you struck the balance between work and non-work in your lives, and how has that related to the culture of the company you were working for at the time? I should also mention the company I work for (early stage, well funded) does have a culture where it’s expected to work everyday, and 60 hours is approximately the minimum expected.

In this episode, Dave and Jamison answer these questions:

1. My company recently eliminated 1:1 meetings between managers and their direct reports. Previously, most people had these meetings every other week, and they were an opportunity to talk about career growth among other engineering things besides current work. They’re claiming the recurring meetings can be replaced with quick, more spontaneous calls when necessary. Although wiping meetings from the calendar does clear up more time to code, as a more junior team member, I’m concerned that this will negatively impact my career growth. It feels like career progression just got a little bit harder. What’s the read here? Is this a red flag? Should I start looking elsewhere? How can I navigate this changing environment and still make sure that I am able to progress my career?

2. A listener named Matt says,

   I’d really like to move to a single team-dedicated backlog, where we use kanban and have work in progress limits, rather that the heavy release planning fixed-scope current model. I feel we would be more effective as a team that way (I’m one of many team leads in the company). Currently we operate in an agile-ish fashion but ultimately inside a waterfall process, driven from outside the technology team. Although I believe it would be a good thing, I’ve not actually worked in that way. Is it all it’s cracked up to be? Are there any issues of going to that model that I’m not seeing?