Post

Of course the author of a merge/pull request should use all available tools to get it in shape before someone else looks at it. The author is the first reviewer. This was true before AI. Besides that I'm team line-by-line, how else can I make sure the software does the right thing?

Rainer Hahnekamp@rainerhahnekamp.bsky.social

1/6 Developers are deeply divided over whether human code review is still necessary. Exaggerating slightly: one side accuses the other of abandoning code quality and blindly trusting AI. The counter is that line-by-line review simply throttles AI back down to human speed. 🐢

11/10/26, 7:48 pm0 reposts8 likes

Lars Hanisch

@flensrocker.de

Do it or don't do it, there is no try... 😎🖖 (Yes, I know it's the wrong emoji...) I'm speaking of software in environments where correctness matters, not a vibe coded script you only use once on some private files...

Joshua Ward | ✝️ | NO AI | Rust! | Simple is better

@joshuaward.roomy.chat

I find that if it's so simple as that, someone else's probably done it before. You can save compute by locating that person and stealing the file off his computer. The neat part is it works, assuming the other person didn't vibe code it.