There are fun and less-fun parts of programming -- building a new feature? Fun. Analyzing requirements, or doing code review, or spelunking through a crappy and undocumented 3rd party API? Less fun. But all can be part of the same 'job' of developing a feature.
The article is saying the amateur is the one who skims off the fun parts, and avoids the others, whereas the professional does the entire job -- gets to done-done, vs just 'it works'.
On golf:
You are correct that Tiger Woods did not pick up the ball on the putting green when playing amateur tournaments. I don't think the article's making a point about the official USGA definition of 'amateur'.
There are fun and less-fun parts of programming -- building a new feature? Fun. Analyzing requirements, or doing code review, or spelunking through a crappy and undocumented 3rd party API? Less fun. But all can be part of the same 'job' of developing a feature.
The article is saying the amateur is the one who skims off the fun parts, and avoids the others, whereas the professional does the entire job -- gets to done-done, vs just 'it works'.
On golf: You are correct that Tiger Woods did not pick up the ball on the putting green when playing amateur tournaments. I don't think the article's making a point about the official USGA definition of 'amateur'.