Resumen del episodio
In 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…
In 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…
Episodios
Episode 533: I'm drowning in AI slop from lazy coworkers
EscuchadoIn 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?
EscuchadoIn 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…
Episode 531: Shallow feedback and my coworker is a huge sloperator
EscuchadoIn this episode, Dave and Jamison answer these questions: Listener Jame ain’t no dance asks,! Hey Space Therapists, I am a consultant that helps big companies to fix all kind of stuff. It’s ridiculous how many different hats I wear. One day I’m the interim PM, the other day I am telling SAP devs how to use a coding agent, next day I gather stakeholder requirements for a customer self service portal. I do all of these tasks on a fairly shallow level and all of that work is happening without much coordination from my company. I think I do a good, but it’s hard gathering feedback on my work, since no colleagues are involved and I can’t simply ask the customer without revealing insecurity. Send sophisticated tips and don’t make me quit. Cheers! Can I tell a coworker to stop using Claude? I work on a small team at a midsized company, and a coworker keeps dropping overly verbose pull requests that are full of AI jargon. These are increasingly hard to understand, and then when I ask for design intent clarification…
Episode 530: Product engineering and why does my team never challenge my ideas?
EscuchadoIn this episode, Dave and Jamison answer these questions: Listener Myamax myamax says, I just listened to episode 527 and could really use some advice on being good at interviews. I was recently laid off with a decent severance package, so I have some breathing space. I’ve had several interviews, and I usually get past the initial screenings, but I don’t shine in technical rounds. I’m a career switcher, and most of my tech career has been in analytics at a big company. I’m good at distilling things, very good at debugging and navigating mazes of corporate legacy, but I haven’t really built things from scratch. I’m not a pure individual contributor, not a product manager but some technical-product hybrid, and it was a fun place to be. I stole good ideas from different teams and stitched them together adding common sense on top. I spent a lot of time with users and stakeholders to understand their data and their processes. Most of the time they needed common sense and decent data foundations. Only in rare…
Episode 529: Zoom calls on my open floor plan and laconic staff engineer
EscuchadoIn this episode, Dave and Jamison answer these questions: Hi Jamison and Dave, jesters of my daily commute. I’m a *mechanical* engineer at a megacorp, and since people are people, I find most of your advice transfers pretty well. I’m the tech lead within a small-ish org of about 25 people. We’re in-office, and split between two locations (in a similar time zone), and multiple different projects. This means that there are a lot of Zoom meetings between locations. Lately, I’ve been having an issue with engineers deciding to take these meetings from their desks in our open office plan rather than finding a phone or conference room. I find this practice to be maddening! It’s really distracting because there will often be background noise that makes it hard to clearly understand them, and it also means that my workplace is a cacophony of people yelling into their AirPods, competing to overcome the background noise of their colleagues’ yelling into their AirPods. How do I make this stop and get my coworkers to hop…