Code reviews are not only about raising quality, but mainly about communicating changes to the wider team. Suggesting to eliminate code reviews when LLM use is so rampant is also quite uhm courageous.

▲

nick4 3 hours ago | parent | next [-]

Communicating changes and communicating learning too! Every few years I rewatch one of my favorite videos on code reviews: https://www.youtube.com/watch?v=PJjmw9TRB7s.

Asking questions on code reviews is one of the most powerful tools to learn more about a codebase, and fostering a culture where junior devs feel empowered to ask questions is one of the best ways to help junior devs succeed.

▲

cloogshicer 5 hours ago | parent | prev [-]

The author never suggested to eliminate code reviews entirely. Just to give individuals more autonomy, which is great in my book.

▲

heyitsdaad 4 hours ago | parent [-]

Hard no buddy. Junior dev means junior code and junior judgement. Countless times we had prod issues because some dev thought the change was harmless and they didn't need review.

▲

cloogshicer 3 hours ago | parent [-]

In the article, they specifically exclude juniors and people who are still being onboarded.

	▲	jinushaun 2 hours ago \| parent [-]
		I can’t find that disclaimer in the article.