4 ms·
The problems I see with the Ship / Show / Ask approach are - How often each is selected will be *very* personality-based and I'm afraid the worst ones will
by pierrebai 5y ago
The problems I see with the Ship / Show / Ask approach are
- How often each is selected will be *very* personality-based and I'm afraid the worst ones will be magnified. AKA "I'm so super good, all my changes are Ship" kinda persons.
- It becomes harder to justify imposing a mode on someone. How do you rein in the ultra-shippers?
- It can become a source of frustration and strife between co-worker. Not just due to the above, but when someone breaks the builds with a Ship and people will start keeping count how many time X broke it, etc.
- With time, I feel there will be drift into less and less Ask.
Basically, freedom to choose is fragile. I think it is better to have an approach were Ship is exceptional, and pretty much everywhere I've work, there has been ways to avoid branching or reviews. I also think that the time-wasting vs time-saved due to reviews is heavily in favor of time-saved. We're no longer in the olden days, we got terabyte disk and easy branching. Starting to work on something else while waiting for a review is easy.