4 ms·
I can imagine that editing code in a fashion similar to Google docs collaboration is the way forward. Especially if tests run continuously, giving instant feedb
by roeles 4y ago
I can imagine that editing code in a fashion similar to Google docs collaboration is the way forward. Especially if tests run continuously, giving instant feedback.
This doesn't mean that daily tests will be a thing of the past, but potential conflicts can be found sooner.
I don't know how commits would work. I feel like they would become a hindrance to productivity, but having atomic changes spanning across multiple files seems like a must for proper rollback scenarios.
- gregmac 4y agoWhen you're doing a big refactor, this would be awful. Sometimes you need to rip out, add, or replace an entire layer or subsystem, and break everything until you're done. I love the freedom having my own private branch gives me to go crazy and demolish whatever I want to see how bad it is to fix. It's like taking out supports in a building to watch how it falls down, then try again. By the time I make a PR I've rebased and cleaned up my commits and made it look like a nice controlled demolition and careful surgical replacement. No one has to see I was ignoring hundreds of complie errors for a couple days.
- roeles 4y agoThis is something that would also be a problem with everybody working on the main branch, which I understand people are doing. I don't know how they deal with large refactoring though.