Linked by MOS6510 on Sun 5th May 2013 22:43 UTC
General Development "In order to be an effective programmer, you need to possess a combination of traits that allow your skill, experience, and knowledge to produce working code. There are some technically skilled developers who will never be effective because they lack the other traits needed. Here are seven traits that are necessary to become a great programmer."
Thread beginning with comment 560632
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Almost not accurate
by lucas_maximus on Mon 6th May 2013 12:10 UTC in reply to "RE[2]: Almost not accurate"
lucas_maximus
Member since:
2009-08-18

That isn't laziness that is being pro-active / constructive.

Edited 2013-05-06 12:11 UTC

Reply Parent Score: 2

RE[4]: Almost not accurate
by JAlexoid on Tue 7th May 2013 12:16 in reply to "RE[3]: Almost not accurate"
JAlexoid Member since:
2009-05-19

Reducing your workload is a form of laziness.

Reply Parent Score: 2

RE[5]: Almost not accurate
by lucas_maximus on Tue 7th May 2013 17:34 in reply to "RE[4]: Almost not accurate"
lucas_maximus Member since:
2009-08-18

ERRR NO.

Reply Parent Score: 3

RE[5]: Almost not accurate
by siride on Wed 8th May 2013 02:23 in reply to "RE[4]: Almost not accurate"
siride Member since:
2006-01-02

Simply not doing work is lazy. Picking efficient ways to do work that you are actually doing is not lazy.

Reply Parent Score: 3

RE[4]: Almost not accurate
by izomiac on Thu 9th May 2013 05:38 in reply to "RE[3]: Almost not accurate"
izomiac Member since:
2006-07-26

It's just semantics. Geneticists call themselves lazy for the same reason. The idea is to work smarter rather than harder, and avoiding hard work is the essence of laziness.

There's probably a dialect issue here as well, because I know "lazy" has historically had much worse connotations than it does today. (At least in my region and age group, in yours it may have retained those implications.)

Reply Parent Score: 1