this post was submitted on 01 Sep 2023
338 points (96.2% liked)

Programming

17553 readers
460 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

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
you are viewing a single comment's thread
view the rest of the comments
[–] TehPers@beehaw.org 3 points 1 year ago* (last edited 1 year ago) (1 children)

You must trust your team's abilities more than I trust my own. How often does your team merge bugs into main? We use CI primarily for running the full test suite, including integration tests and e2e tests that would be very difficult to run locally due to them using specific credentials to access testing resources.

[–] vvv@programming.dev 1 points 1 year ago (1 children)

If your team consists of people you don't trust, that's the problem to fix first.

[–] TehPers@beehaw.org 1 points 1 year ago (1 children)

I trust my team. I don't trust my or their ability to write and merge perfect code each time. I'm not sure how we'd fix that problem aside from becoming programming gods.

[–] vvv@programming.dev 1 points 1 year ago

My point is, having PRs desn't result in perfect code either. They might help sometimes, maybe 10% of the time if I'm being generous, but the rest of the time they are a hindrance. The problems people tend to try and solve with them, validation and indoctrination are better solved with a good CD pipeline, and pairing sessions.