Laziness when you do wait for answer on your "how to do it with one statement" question at forums.oracle.com
Patrick
· 3 years ago
Ha! The pic is sooo funny! Sad, but funny.
ouch! I am so guilty on a number of your statement, but this one hits home the most:
"Laziness is when you do not check out what’s new in new versions."
I am going to print this list out and hang it up in the cube.
Gary
· 3 years ago
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.
Rob V
· 3 years ago
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.
Karl
· 3 years ago
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.
Karl
· 3 years ago
The picture could also have the tilte 'Ways to show Respect to Nature' ;-)
Taps
· 3 years ago
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. :)
Jim Cassella
· 3 years ago
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"
APC
· 3 years ago
Have you read Philip Lenssen's article "Why Good Programmers Are Lazy and Dumb"? It's well worth reading
Yes good read indeed, in fact, I link to and quote part of his article in my post above.
vidya
· 3 years ago
“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.
APC
· 3 years ago
in fact, I link to and quote part of his article in my post above.
All Comments
Laziness when you do wait for answer on your "how to do it with one statement" question at forums.oracle.com
ouch! I am so guilty on a number of your statement, but this one hits home the most:
"Laziness is when you do not check out what’s new in new versions."
I am going to print this list out and hang it up in the cube.
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.
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.
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.
The picture could also have the tilte 'Ways to show Respect to Nature'
;-)
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. :)
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"
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
APC,
Yes good read indeed, in fact, I link to and quote part of his article in my post above.
“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.
in fact, I link to and quote part of his article in my post above.
Doh! How dumb does that make me :(