What’s your take on oversized Pull Requests? Knowing that it’s the norm of AI assisted development, automation hasn’t still caught up with humans reviewing the changes.. I would and still reject overly large PRs for reasons outside of testing and fixtures.

With all the layoffs and general anxiety about what's next, I’m seriously overworking myself. I’m scared that if I don’t, I’ll get let go and never find anything else in this field. If you recently went through a job search, how long did it actually take?

How are your daily standups run? Yeah, some people throw in blockers here and there but it’s really just people talking about how productive they were the day before by listing their accomplishments. It’s not the time or place for that. I think stand ups should just be revised to “is there anything stopping you from during your work that the entire team needs to know”?

What’s the “worst” codebase you’ve ever worked in? I oversee a handful of legacy of inherited services and am finding incremental ways to deprecate/sunset what I can. It has a ton of dead code but it isn’t even the worst I’ve seen. Projects with old libraries that aren’t supported, database layers woven in, and no linting/types.

In my ten years as a software engineer, I’ve discovered a bizarre trend that smooth projects often get less recognition than chaotic ones. It may be due to a perception that it must have been an easy project if it was so smooth. On the other hand, projects with multiple day follows, dramatic reverts, etc get a ton more visibility. Have others seen this on their organization?