The hosts discuss the return to the office and quitting tech. They explore the challenges of commute time and paycuts, as well as the uncertainty of layoffs. They also touch on parking allowances and perks in tech companies, burnout in the tech industry, and navigating personal and professional growth.

Visa rejection and its impact on professional competence. Dealing with a co-worker's constant mistakes and opposing mindset. Creating a comprehensive guide to software engineering mistakes. Navigating the Daily WTF blog and addressing the challenges of working with Bob.

Topics discussed: dealing with burnout and whether to inform your manager, challenges and tensions of joining a new team in a lead engineer role, strategies for success in leadership positions, the importance of humility and collaboration, and team building activities like science fairs.

The podcast discusses the importance of having a vision in the tech industry and explores the challenges of predicting the future. It emphasizes the need to gather data and understand customer needs to build a bigger vision. The hosts also provide advice on handling a negative work environment and navigating the tech job market. They share a frustrating meeting experience where a senior colleague disregards previous plans, leading to the speaker leaving the company.

The podcast discusses challenges of startup equity and valuation, navigating conversations about equity with managers, and the frustration of being interrupted in remote meetings, including solutions like raising hands and using the chat feature in Zoom.

Topics discussed include feeling inadequate compared to a predecessor who went above and beyond, interpreting nice things about previous employees as criticism, living up to the reputation of a predecessor, and the frustration of being left off a list of contributors.

The podcast discusses gaining confidence as a developer, imposter syndrome, understanding covariance and contravariance, and building a CSV importer. They also touch on differences in perspectives between employees and bosses.

This episode is sposored by OneSchema, the best way to build CSV import into your product. Check OneSchema out at https://oneschema.co/softskills In this episode, Dave and Jamison answer these questions: My employer offered a retention bonus after: The CTO left two weeks after I arrived Two weeks later 1/4 of the staff was laid off Two weeks after that the COO left Two weeks after that 2 board members resigned Three or Four weeks after that the Director of Engineering left What does that mean? What do I look out for? I discovered your podcast just about 2 weeks ago and I love it, and I listen to them daily when driving to office, this make forced RTO feels a little bit better. I am currently a mid to senior SWE at FAANG. For the past 1.5 years I have been trying to interview for other opportunities at Staff level. I have good result with coding and design interview but I felt like I’m always falling short at behavioral questions. Example is “Tell me a time when you have a conflict”. How do I go about showing seniority in these type of questions? I led a few projects and powered through a lot of conflicts to deliver results at my company, at the same time I can’t think of a particular methodology I used to get through them. There were times I compromised, pushed back hard, meet halfway depends on situation. I dont want to show i’m a pushover at the same I don’t want to show i’m not easy to work with. What are the signals they are looking for for a Staff level engineer in behavoral style questions

In this episode, Dave and Jamison answer these questions: I am a senior engineer working in a team of 7. My team lead went through a pretty rough divorce in December. Since then he’s been quite distracted and disengaged at work. I decided to help him out by temporarily taking on some of his responsibilities. Over the months things seemed to have gotten worse. He shows up late for the 10am standup meeting almost every day. He never contributes anything in stakeholder meetings. I am effectively leading the team at this stage. Last week we had a one-on-one meeting to conduct my annual performance review. I wanted to discuss my situation and a potential promotion/raise. Instead he spent the entire hour crying about his life situation. He also shared with me that he has been heavily drinking and doing drugs for the past few months. He is clearly in a very dark place. I have experience with depression so I was able to empathize and offer some advice. I genuinely feel bad for him and I’m a quite worried that he might not be OK. But now I’m in a difficult situation. I’m sleep deprived while trying to do the job of de-facto team lead/manager as well as my regular senior/IC role. I don’t think anyone in HR or management is aware of what is going on. I don’t know what to do about this. I feel that if I tell HR about the situation that I will be betraying his trust. (and I might even get him fired depending on how much I divulge) On the other hand if I do nothing then I’m the one who has to keep shouldering the burden without compensation. It’s also negativity impacting the team as I have no management experience while simultaneously my code quality is suffering. This is putting me under a lot of stress during a time when I’d love to spend more time with my newborn. Sorry for the long and difficult question. Even if you don’t answer it at least I feel better for sharing this with someone :) Hi there! Long time listener, first time caller. I’ve been working at a small, seed stage startup for a little over a year as a senior IC and team lead. There are developers on another team who have been working at the company longer than me who have… questionable practices. For example, in production they set their log level to debug because they claim it is critical for them to find and fix bugs. However I’ve never seen or heard of an example of them actually using these logs to fix a problem, and this results in log spam and higher cloud costs. Whenever I try to open a dialogue about this or another one of their practices, they’re quick to deflect and insist on not changing anything. They don’t get defensive but just don’t want to do anything differently. Usually I give them my opinion and let them handle their own services but we’re seeing real financial costs to their decisions. I know our greatest costs are on people but I think we should still be responsible with our cloud spending. How can I get these other developers to Quit Their Job™ or otherwise be more open to new ideas for their practices?

In this episode, Dave and Jamison answer these questions: We’ve recently switched to mandatory 2 days of in-person work a week but my employee keeps working from home! Whenever I ask him to come in person he says sure but continues to work from home. When I confront him about not showing up in person he just says “sorry I wasn’t able to make it that day”. He’s a good employee so I don’t want to fire him, but I’m concerned about what upper management will say if/when they find out about this. What should I do? Hi! I am a huge fan of the podcast and a longtime listener. I recently made a professional judgment call in a high-stress situation that, unfortunately, did not turn out well. It was an excellent learning opportunity for me. Both my team and mentors were very supportive and said they’ve all fumbled at one point in their career. I was understandably reprimanded in a private meeting with my manager. I embarrassingly started crying halfway through, which I’ve NEVER done before in a professional setting. I momentarily excused myself to regain my composure, but even after resuming I had to keep the the tissue box close by. It was awkward, and I could tell my manager was very uncomfortable despite being his kind demeanor. I am worried my reaction will call my reputation and professionalism into question. Please help! How do I recover from this?