Golf and Programming

I played golf twice this past weekend - not terribly well, but it was fun and the weather was great here in Virginia.
So, I was wondering, how is Golf like programming ?

  • Plan your strategy - In both, you must plan your strategy before "teeing off". As a programmer, it is very helpful to have at least a minimal plan or design in place before writing some code. It saves work in the long run and avoids costly re-writes and redesigns midway through the job. In Golf, you should evaluate each hole layout before teeing off so you know what club to use. You should have an image in your mind about the shot you want to make, it's never good to just hack it around without at least some preliminary planning.
  • Don't Rush It - Don't rush your shots in golf, take your time and make a smooth swing. Don't rush your code, let it develop naturally and don't cut corners.
  • Use the right tools - Some golfers are addicted to the equipment, always upgrading to the latest/greatest technology and trying to gain an edge with $$ and technology. This is usually not a successful strategy. Its always better to use the "right" tools for the job, sometimes sticking with your trusty old driver and putter is better than getting the shiny new model from the store. In programming, having a great set of tools for the job and knowing how to properly apply them often improves your productivity. However, sometimes the shiny new technology just distracts you from the core task and decreases your overall productivity by taking your attention away from the code that is being produced.

Comments:

Post a Comment:
Comments are closed for this entry.
About

wyllys

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today