You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we want to include more style tips in our Stata trainings? — e.g., indent after an open brace. I find that many people start at IPA with an unprepossessing style, but not because they prefer it: they just haven't been exposed to alternatives or told why style is important. They could be introduced to style early on, even before 103...
Interesting, my gut is that we should not include style too much within the body of the training (I feel it's likely to be glossed over) but certainly link to outside resources, which I think is already done. Though I agree introducing style a bit earlier is a good idea. Besides in 101, we never really show what a good do-file looks like, and in 101 it's probably too early to have people actually appreciate it. Perhaps in the future we have a problem set question where one has to identify the style errors in a do-file.
Do we want to include more style tips in our Stata trainings? — e.g., indent after an open brace. I find that many people start at IPA with an unprepossessing style, but not because they prefer it: they just haven't been exposed to alternatives or told why style is important. They could be introduced to style early on, even before 103...
Existing resources:
http://www.stata-journal.com/sjpdf.html?articlenum=pr0018
https://ipastorage.box.com/s/eth7131k23r66bsdoxs4
I think the dream would be a style guide like this one for C++ (though ours would be much shorter!):
http://geosoft.no/development/cppstyle.html#Naming%20Conventions
The text was updated successfully, but these errors were encountered: