2 ms·
Access to all/some contributor's local git repository is a powerful capability but you need to think deeply about 1 or 2 core use cases. "Pull up a chair" is on
by amirathi 8y ago
Access to all/some contributor's local git repository is a powerful capability but you need to think deeply about 1 or 2 core use cases. "Pull up a chair" is only a surface activity, what's the user's real intent here? Is she trying to understand some part of the codebase or pair programming or debugging together? How can CoDiff help in that core activity?
To get you started here's something I would find useful,
- If I am starting to edit parts of the code that would create conflict with remote or peer's local state, just send us a notification. Much easier to avoid merge conflicts than resolving them.
Also think of developer psychology, e.g. I don't want peers to randomly peek into my WIP code. Things of that sort. Good luck!
- jtsiskin 8y agoThank you for this! It is very true we need to focus on 1 or 2 key features. The real intent of 'pull up a chair' is to be able to discuss WIP code together and help decide and debug. Working next to my coworkers I often show them my screen and ask them questions about what I'm currently doing; we hope CoDiff can give this ability to all teams, local and remote. We agree completely with the first bullet point - that is one of our key features we have found useful. The second point is very interesting. What would you say is the reason you don't want peers peeking at your WIP code? We were wondering if it could be beneficial and have an effect similar to https://news.ycombinator.com/item?id=19591227 https://news.ycombinator.com/item?id=19591227