Comments on: Do You Have These Symptoms?

By: APC

APC — Fri, 01 Dec 2006 10:02:48 +0000

in fact, I link to and quote part of his article in my post above.

Doh! How dumb does that make me

By: vidya

vidya — Thu, 30 Nov 2006 18:26:20 +0000

â€œLaziness is when you do not check out whatâ€™s new in new versions.â€ - agreed this hits home the post - the zillion new features with every version has been kind of hard to keep up with and just before you have taken advantage of all the new features you are on the roll for the next version upgrade.

By: Eddie Awad

Eddie Awad — Thu, 30 Nov 2006 17:30:08 +0000

APC,

Yes good read indeed, in fact, I link to and quote part of his article in my post above.

By: APC

APC — Thu, 30 Nov 2006 17:23:45 +0000

Have you read Philip Lenssen’s article “Why Good Programmers Are Lazy and Dumb”? It’s well worth reading

http://blog.outer-court.com/archive/2005-08-24-n14.html

Cheers, APC

By: Jim Cassella

Jim Cassella — Wed, 29 Nov 2006 21:48:55 +0000

I couldn’t agree more. My favorite quote ever was from my first boss, who said “If you give the laziest guy the hardest job, he’ll find the easist way to do it”

By: Taps

Taps — Wed, 29 Nov 2006 07:49:52 +0000

The more experienced I get the more lazy I become. I always say why look for new features when the ones I have can do the job well.

By: Karl

Karl — Wed, 29 Nov 2006 07:05:50 +0000

The picture could also have the tilte ‘Ways to show Respect to Nature’

By: Karl

Karl — Wed, 29 Nov 2006 07:03:59 +0000

never forget the good site of lazyness; a lazy dba does not manually repeat a way again and again. He will find a way to automate it.

One major reason i create solid structured reliable code is that i am to lazy walking throug spaghetty code.

Karl very lazy dba and database architect.

By: Rob V

Rob V — Tue, 28 Nov 2006 23:57:38 +0000

In fairness, laziness is rewarded.

One time my only negative tick on a performance review was that I wasn't sensitive to budgetary concerns and insisted on doing everything properly. They said sometimes they just wanted quick and dirty and I was always reluctant to do so.

Our compromise was just for them to go to someone else when they had something (presumably unimportant) half-assed and wanted corners cut, but come to me when they had something they needed done right.

However, the corner-cutters were the stars because of the sheer amount of crap they produced.

In any event, there's good lazy and bad lazy. Good lazy is taking a little extra time to document, test and modularize your code so you can reuse, fix and enhance it later with little effort.

By: Gary

Gary — Tue, 28 Nov 2006 22:53:55 +0000

Laziness is when you see a bug in the code, but you don’t fix it.
Laziness is when, rather than add a new column to a table, you concat two separate attributes into a single column.
Laziness is when you don’t put in the check constraint
Laziness is when you code a program path, and don’t test it.
Laziness is global variables.
I can go on and on and on.