Wandering around in the weeds

[ViAnn Beadle]

I have seen a number of recent threads in which extended discussions seem to not resolves posters’ queries satisfactorily and they remain wandering around in the weeds. Common themes and possible solutions are:

1)      Macros are confused with basic syntax. RTFM. Do not try to wrap syntax in a macro until the syntax runs correctly. Do not debug the syntax by running it all at once.

2)      Transformations are used in place of reporting procedures like CROSSTABS, TABLES, SUMMARIZE, …

3)      Data are not in the right shape for a given procedure. CASESTOVARS and VARSTOCASES seem to be the frequent solutions to knotty problems.

4)      The poster has obtained some syntax that they don’t understand and can’t debug. Don’t understand what a COMPUTE command does? Run it and click on the Run Pending Transformations and look at the results in the data window.

5)      A lengthy set of transformations and data management functions don’t work as expected. Run the logical blocks and look at the results in the data window.

6)      Vocabulary differences. Script, syntax, and macro mean very different things. Poster and respondent need to come to a common understanding of what each of these things mean.

7)      It’s difficult to diagnose a poster’s problem with incomplete information. It is especially difficult if the poster is using a dialog box or wizard and is unaware that syntax is being generated and executed.

8)      Posters may expect that their questions will be answered freely and promptly. That isn’t going to happen if there is significant mismatch between the user’s knowledge and experience and the scope of the problem. Respondents assume that the poster knows a lot more about their problem or the domain than they really do. Much better for the poster to seek help locally or hire a consultant who has the time to spend on the problem.

Shields up.

[Gary Oliver-3]

Hi ViAnn

 

Yup, agree with everything you say. Would only add the recommendation for beginners to use the paste command from the windows dialog to get the basic syntax as a starter and be prepared for some trial and error from there

 

Warm regards/gary

 

From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of ViAnn Beadle
Sent: Monday, March 18, 2013 3:00 PM
To: [hidden email]
Subject: Wandering around in the weeds

 

I have seen a number of recent threads in which extended discussions seem to not resolves posters’ queries satisfactorily and they remain wandering around in the weeds. Common themes and possible solutions are:

1)      Macros are confused with basic syntax. RTFM. Do not try to wrap syntax in a macro until the syntax runs correctly. Do not debug the syntax by running it all at once.

2)      Transformations are used in place of reporting procedures like CROSSTABS, TABLES, SUMMARIZE, …

3)      Data are not in the right shape for a given procedure. CASESTOVARS and VARSTOCASES seem to be the frequent solutions to knotty problems.

4)      The poster has obtained some syntax that they don’t understand and can’t debug. Don’t understand what a COMPUTE command does? Run it and click on the Run Pending Transformations and look at the results in the data window.

5)      A lengthy set of transformations and data management functions don’t work as expected. Run the logical blocks and look at the results in the data window.

6)      Vocabulary differences. Script, syntax, and macro mean very different things. Poster and respondent need to come to a common understanding of what each of these things mean.

7)      It’s difficult to diagnose a poster’s problem with incomplete information. It is especially difficult if the poster is using a dialog box or wizard and is unaware that syntax is being generated and executed.

8)      Posters may expect that their questions will be answered freely and promptly. That isn’t going to happen if there is significant mismatch between the user’s knowledge and experience and the scope of the problem. Respondents assume that the poster knows a lot more about their problem or the domain than they really do. Much better for the poster to seek help locally or hire a consultant who has the time to spend on the problem.

Shields up.

[David Marso]

AMEN ViAnn!
I think I will bump this to the top about once a week so it maintains visibility.
Tempted to bump my "how to ask questions thread" too, but that posting didn't seem to make one bit of difference?

To Clarify one thing:
RTFM means "Read The Fine Manual" (just in case some thin skinned thick-skullian might fear otherwise).

I will add as well:  Frequently people return with additional questions out of the blue which are  related to other questions recently posted (i.e followups).  I ask that rather than rely on the memory of list members, please refer to the previous thread and summarize and relate to present.
I am blessed/cursed with something close to a photographic memory so nothing really gets past me in that regard.

ViAnn Beadle wrote

I have seen a number of recent threads in which extended discussions seem to
not resolves posters' queries satisfactorily and they remain wandering
around in the weeds. Common themes and possible solutions are:
1)      Macros are confused with basic syntax. RTFM. Do not try to wrap
syntax in a macro until the syntax runs correctly. Do not debug the syntax
by running it all at once.
2)      Transformations are used in place of reporting procedures like
CROSSTABS, TABLES, SUMMARIZE, .
3)      Data are not in the right shape for a given procedure. CASESTOVARS
and VARSTOCASES seem to be the frequent solutions to knotty problems.
4)      The poster has obtained some syntax that they don't understand and
can't debug. Don't understand what a COMPUTE command does? Run it and click
on the Run Pending Transformations and look at the results in the data
window.
5)      A lengthy set of transformations and data management functions don't
work as expected. Run the logical blocks and look at the results in the data
window.
6)      Vocabulary differences. Script, syntax, and macro mean very
different things. Poster and respondent need to come to a common
understanding of what each of these things mean.
7)      It's difficult to diagnose a poster's problem with incomplete
information. It is especially difficult if the poster is using a dialog box
or wizard and is unaware that syntax is being generated and executed.
8)      Posters may expect that their questions will be answered freely and
promptly. That isn't going to happen if there is significant mismatch
between the user's knowledge and experience and the scope of the problem.
Respondents assume that the poster knows a lot more about their problem or
the domain than they really do. Much better for the poster to seek help
locally or hire a consultant who has the time to spend on the problem.

Shields up.