3 ms·
Fundamentally, because of "reduction of steps" [1], although the workflows might be otherwise functionally equivalent: (1) The cognitive overload of the git pu
by abhgh 6y ago
Fundamentally, because of "reduction of steps" [1], although the workflows might be otherwise functionally equivalent:
(1) The cognitive overload of the git push and pull - while this might have seemed small when I was using this workflow, I don't have these steps anymore making them seem unnecessary in retrospect. Reduced steps in general are better IMHO: same reason as to why I might use something like Google docs, even though, a somewhat equivalent workflow would involve going via GitHub.
(2) Ensuring all local environments are similar or identical. Esp. a problem when installing new packages, say on device 1... when compiling on device 2, I need to either remember to do this by noting it somewhere (e.g. modifying the makefile), or I am reminded of it with a compilation failure.
Small gains perhaps, but they add up. Esp. if you are working on multiple documents at the same time (I typically have 2-3 active documents).
[1] If it matters, I need to switch between 3 devices running windows, ubuntu, elementary OS.