4 ms·
> but this has significant disadvantages and practically no advantages (other than "accuracy of what happened". ...which is a very big advantage, big enough th
by bigstrat2003 13d ago
> but this has significant disadvantages and practically no advantages (other than "accuracy of what happened".
...which is a very big advantage, big enough that it outweighs the disadvantages in my opinion.
- rgoulter 13d agoCan you help provide examples from your development experience where "knowing the accurate history of what happened" was a very big advantage, to the extent where not having this knowledge would have made things very difficult?
- otherme123 12d agoHere a developer thought that redis would be a good add to the stack, so we decided he should try. It turned out that it didn't fit, mainly because it needed to touch code in more places than anticipated. We went back to starting point, but the project now carries a "no more redis/cache attempts before reading this one, please" fossil. New attempts can't say "oh, I didn't know this was attempted before". With git, this kind of experiment would be hidden with a "reset hard", and probably will happen again when people forgets, someone says "didn't we try that a year ago?" but we have no records. This is very helpful in small private teams, not so much in biggest teams (kernel), pass-by PR environments (github), or public CV-oriented repos (no mistakes allowed there, only pretty linear timelines).