That mismatch worked, if uncomfortably, when contributing had friction. After all, you had to care enough to reproduce a bug, understand the codebase, and risk looking dumb. But AI agents are obliterating that friction (and have no problem with looking dumb). Even Mitchell Hashimoto, the founder of HashiCorp, is now considering closing external PRs to his open source projects, not because he's losing faith in open source, but because he's drowning in "slop PRs" generated by large language models and their AI agent henchmen.
Lead without authority. You may not have direct reports, yet you shape architecture, quality and the roadmap. Your leverage comes from artifacts, reviews and clear standards, not from title.I started by publishing a lightweight architecture template and a rollout checklist that the team could copy. That reduced ambiguity during design and cut review cycles by nearly 30 percent
I pointed out that for software engineers, the code is the product. For research, the results are the product, so there's a reason the code can be and often is messier. It's important to keep the goal in mind. I mentioned it might not be worth it to add type annotations, detailed docstrings, or whatever else would make the code "nice".
