3 ms·
I find it plausible that a golf cart could make somebody better at golf. Without the cart, a non-trivial amount of exertion is spent on a tangentially related
by jlgreco 13y ago
I find it plausible that a golf cart could make somebody better at golf. Without the cart, a non-trivial amount of exertion is spent on a tangentially related task (getting from hole to hole) instead of on the primary task (getting the ball from hole to hole). Something that allows golfers to better focus on golfing could conceivably improve their game.
- kristopolous 13y agook then: "A paintbrush in hand doesn't make you Monet"
- dingaling 13y agoIn my experience as a non-participating attendee, very little of non-professional golf is actually about the ball and the holes. Most of it is about what is discussed when walking between holes; to that end, a golf cart would be detrimental to the 'purpose'.
- gaoshan 13y agoI really get tired of this sort of response where the one replying ignores the primary point in order to take issue with a single portion of one of several examples that bolstered it.
- jlgreco 13y agoI am not ignoring the primary point. My point about golf-carts and better golfers maps back onto branching and better programmers. To spell it out explicitly: I believe that modern version control systems, specifically ones that provide sophisticated branching facilities, reduce mental load on programmers and speed up tedious tasks. This could very well make people who take advantage of them better programmers (where "better" can be described in terms of efficiency). The less time I spend managing branches and doing merges/rebases the old way, the more time and effort I am able to devote to my primary task (actually programming). I could manage patch files and tarballs with quilt, but I would be wasting my time and my productivity would drop. That would make me a "worse" programmer. If bad tools can hold me back, then better tools can improve me.