Programming

18916 readers

388 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 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

The Power of Code Reviews: Building Better Software and Stronger Teams (thefranconiancoder.studio)

submitted 22 hours ago by cm0002@lemmy.world to c/programming@programming.dev

3 comments fedilink hide all child comments

top 3 comments

sorted by: hot top controversial new old

[–] cool@lemmings.world 3 points 16 hours ago* (last edited 16 hours ago) (1 children)

A problem with code reviews is that sometimes it's easier to reason about a problem as you work on it. You will likely end up with better code going through an iterative process working with your computer instead of trying to get the perfect solution the first time.

It's kind of like math. We need to expand a problem out in order to solve it, and then simplify the solution once we have it.

[–] MajorHavoc@programming.dev 5 points 14 hours ago* (last edited 14 hours ago) (1 children)

I mean, you're allowed to test it before it and iterate goes to review, though.

And reviewers can be allowed to merge stuff that's "good enough", and the iterate.

[–] cool@lemmings.world 2 points 9 hours ago

Of course. Code review doesn't have to be a strict process.