alt Hacker NewsThis part toward the end of the article resonated with me:
> If you’re being asked to review huge volumes of terrible AI code, just assume that the organisation is going to burn you out and fire you. You will not convince the person drowning you in 2000 line PRs to stop. Start looking for a new job as if you have already been fired. I have seen this happen many times now
I suspect we will see this phenomenon more and more as organizations more widely adopt agentic development.
Replies
osmsucks • last Sunday at 8:15 AM
I'm in this quote and I don't like it.
eudamoniac • yesterday at 1:26 AM
My F100 corporation has answered this problem by removing code review entirely. Thankfully it's not Boeing or anything important. Yes I am looking desperately for a new job.
➕ show 2 replies
I don’t buy it - if you’re an engineering leader and this is happening it’s your responsibility to get out there and fix the problem through education, process improvements, improved automated quality checks, better planning. Sticking your fingers in your ears and shouting “no!” is not a sustainable strategy. Figure out what would allow your throughput to double, triple etc and go organise it. Focus on bottlenecks and the most difficult pieces. I’m speaking from active experience here.