Programming

28004 readers

287 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

What are code reviews even for? (newsletter.getdx.com)

submitted 1 day ago by codeinabox@programming.dev to c/programming@programming.dev

5 comments fedilink hide all child comments

If the answer were as simple as “finding defects,” then a fully automated review starts to sound inevitable (and appealing).

But if code review was also how teams shared knowledge, built collective ownership, spread architectural understanding, and taught junior engineers how experienced developers think, then the answer becomes much less obvious.

That’s the mistake I think many organizations are about to make, and the reason we need to rethink what code review is actually for.

you are viewing a single comment's thread
view the rest of the comments

[–] jtrek@startrek.website 14 points 1 day ago

A large part of code review has been preventing people from doing stupid shit. AI is making stupid shit worse. It's not defects, it's "adding a whole micro service to get the user name from the ID, when the name is already in the metadata" or whatever that recent meme was.

Or that time a guy wrote a whole DSL instead of using the existing framework. Technically impressive, but adds a huge burden.