this post was submitted on 03 Jul 2023
37 points (93.0% liked)

Programming

17433 readers
212 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] sudo@lemmy.fmhy.ml 6 points 1 year ago (1 children)

Exactly my reaction as well. The only 'benefit' she lists that I can truly see is 'greater visibility into the code everyone else is working on' but frankly that seems like it could be a burden as well.

Sometimes you don't need to know. If your team organizes it's projects and assignments well, you very well may be able to work on your small piece and integrate it without really needing to know every little thing every other person is working on.

With frequent commits branches just seem like an easier way to resolve conflicts as well as speed up the ability for others to test and merge their changes while you can resolve issues with a build.

[โ€“] Olap@lemmy.world 5 points 1 year ago

You can also typically see team mates branches in repos... Seems they are just missing SVN?