Technically Correct Is Not Necessarily the Best Form of Correct
- External reference:
- External reference: https://www.allthingsgit.com/episodes/branching_and_merging_part_2.html
See pragmatisme, eating your own dog food, ivory tower effect.
Technically correct is not necessarily the best form of correct
— https://www.allthingsgit.com/episodes/branching_and_merging_part_2.html
This quote was meant to say that by looking at how git works relativity to versioning, it looks less elegant than competitors, like mercurial (in the opinion of the author of the quote). And yet, when using it, it feels better. This is an example that looking for a great theoretical stuff does not necessarily lead to a good practical tool.
Notes linking here
- difference between engineering and theory is that engineering makes trade-offs
- Dogfooding et paire de rollers
- pragmatic git workflow (blog)