[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

st: two steps of writting commands

From   Mandy fu <>
Subject   st: two steps of writting commands
Date   Thu, 12 Feb 2009 01:10:01 -0500

Dear Statalisters,

I 'm curious about the steps  used to write do files. I find usually I
need to do two main steps:
First, write the original commands, check the outputs, test for
various models, compare the results, select some models and report the
results. This is like the draft version of commands.

Second, organize and edit the original commands for future use or
audit:simplify the commands(for example,using programming commands to
substitute similar commands) , delete the redundant ones, make the
commands neat.
When  working with step 1, my goal is to get the job done. Sometimes I
cannot think too much about how ugly the commands look like. This is
why I need the second step to polish  what I get from step 1.

I was wondering if I sould combine these two steps together.  Should I
take consideration of getting the commands simpler, more concise,and
more transparent in step 1 so that I don't need step 2 at all? Is the
two-step way usual or most people don't need the second step? Any
comments will be helpful.  Thanks a lot!

*   For searches and help try:

© Copyright 1996–2023 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index