Which Problem Are You Solving?

Question

Which Problem Are You Solving?

Steve Jones - SSC Editor

SSC Guru

Points: 734416
More actions
January 24, 2015 at 11:32 am

#314815

Comments posted to this topic are about the item Which Problem Are You Solving?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1003851 More actions · Answer 1

Steve Jones - SSC Editor (1/24/2015)
Comments posted to this topic are about the item <A HREF="/articles/Editorial/121702/">Which Problem Are You Solving?</A>

Since 90% of any effective solution is the correct identification of the problem and that a lot of people never actually take the time to correctly identify a problem but still issue Draconian edicts and supposed "best practices" (most BPs are well though out but there's some real doozies out there), I think that's a great question.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Ryk Say Hey Kid Points: 682 More actions · Answer 2

I don't think that every issue needs to be solve to the root cause. There are plenty of times something goes sideways on one of my computers and a reboot fixes the issue. I'm fine with that, but if it occurs more than two or three times, I do need to solve the problem.

It took me a while to learn this lesson. There are too many one-time problems that happen, so I learned not to even worry about something unless I see it at least twice. This is one piece of advice that I think should be passed on to just about anybody in a troubleshooting role.

Gary Varga SSC Guru Points: 82166 More actions · Answer 3

ryk 98103 (1/28/2015)
I don't think that every issue needs to be solve to the root cause. There are plenty of times something goes sideways on one of my computers and a reboot fixes the issue. I'm fine with that, but if it occurs more than two or three times, I do need to solve the problem.
It took me a while to learn this lesson. There are too many one-time problems that happen, so I learned not to even worry about something unless I see it at least twice. This is one piece of advice that I think should be passed on to just about anybody in a troubleshooting role.

...but not as a best practice 😉

This is an option to be considered not a rule to be applied. I think that anyone who did this as standard would convert a huge number of friendly colleagues to infuriated colleagues overnight.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!

Steve Jones - SSC Editor SSC Guru Points: 734416 More actions · Answer 4

Perhaps, but I often don't overreact on the first occurrence. I think there are many one time events, and it isn't necessarily worth chasing them all down.

Certainly it's a judgment call, but I tend to want a repeat issue before I worry too much about it.

Gary Varga SSC Guru Points: 82166 More actions · Answer 5

Steve Jones - SSC Editor (2/11/2015)
Perhaps, but I often don't overreact on the first occurrence. I think there are many one time events, and it isn't necessarily worth chasing them all down.
Certainly it's a judgment call, but I tend to want a repeat issue before I worry too much about it.

Jeff will sagely say "it depends" so hopefully I will have saved him the effort. 😉

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!