7 ms·

during those cases, i've just asked them to give me control over zoom and it's worked fine. I've never desired to have two people working on the same file at t

• saghm 1mo ago
  Even if you're not both typing at once, being able to trade off quickly without having to manually pass the ownership back and forth has had value for me in the past.
  • 8n4vidtmkvmk 1mo ago
    Can you elaborate? Why wouldn't you just check in your code when you're done your bit instead of working on the same commit together?
    • nugator 1mo ago
      I like it because we don't have to do the this dance all the time: * Commit * Push * Say: Now it's pushed * Pull We can just work together, talking and writing code. Works great with people you work well with and are aligned with.
    • saghm 1mo ago
      This feels a bit like asking why I would send my coworkers a Slack message instead of an email. For some things, send and wait for them to look at it is fine, but if I want to have a conversation, it's a lot less work to use something that's real-time. If we're both working on nice modular features, and they just need to use the code I wrote as-is (or only make some small targeted changes that they can do without my help), git branches are useful. Sometimes it's been useful to be able to prototype something in real-time while bouncing ideas off each other or if I'm trying to help them get something specific working in their code (but I don't have nearly as much familiarity with the other parts of what they're doing).