Which one is better in version control?

21 Tem 23:14

Yeah, these kinds of discussions always come up, but I think the answer really depends on your project. I was working with a small team on a startup project recently, and everyone was developing in their own branches in a distributed way—then the merge process turned into a nightmare. I remember spending a whole week resolving conflicts one by one, especially because of frontend/backend clashes, before sending anything to the testers. After that, we switched to a centralized repo (GitHub) with a strict PR process. Every PR had to go through at least two reviews, and we kept the commit history clean with interactive rebase. So yeah, we kind of combined the best of both worlds—distributed and centralized. Result? We got faster, and the merge headaches dropped. So, you gotta experiment a bit and see what works for you!

22 Tem 00:10

Thanks for opening this topic, it adds interesting perspectives to all of our preferences. Do you prefer a messy, decentralized codebase or a more centralized system in practice?

22 Tem 02:14

Everyone's using Git while I'm still stuck in the "what does commit even do? Why not just delete and be done with it?" mindset 😅 Honestly, even when my workspace is a mess, I still feel like I'm working with a centralized system.