{"id":570,"date":"2010-07-04T02:33:11","date_gmt":"2010-07-04T07:33:11","guid":{"rendered":"http:\/\/www.thejuliagroup.com\/blog\/?p=570"},"modified":"2010-07-04T02:37:31","modified_gmt":"2010-07-04T07:37:31","slug":"signs-youre-not-a-novice-programmer","status":"publish","type":"post","link":"https:\/\/www.thejuliagroup.com\/blog\/signs-youre-not-a-novice-programmer\/","title":{"rendered":"Signs you’re not a novice programmer"},"content":{"rendered":"
\"I'll
I'll get this down eventually<\/figcaption><\/figure>\n

Writing a presentation for WUSS<\/a>, I had to fill out the usual check box for the intended audience:<\/p>\n

Level of programming expertise:<\/p>\n

___ Novice __ Intermediate __ Advanced<\/p>\n

and I started wondering when exactly does someone stop being a novice? One answer is that your programming no longer LOOKS like it was written by a novice. That’s kind of circular reasoning, though, isn’t it? To be more specific, here are a few of those signs, generated from a survey of a random sample of 1.<\/p>\n

(Note, if your programming does not always show all of the characteristics mentioned below, you are forbidden to feel bad. All but a very exceptional few programmers will admit to having made every ‘newbie’ mistake when they started, and on occasion, they still do when they are rushed, tired or distracted by three fighting children or after their third martini. As for that exceptional few – they’re chronic liars. Stay away from them.)<\/em><\/p>\n

Five signs you’re no longer a novice, in no particular order ….<\/p>\n

1. Good use of functions<\/strong><\/p>\n

AvgQtr = (Jan + Feb + Mar) \/3<\/p>\n

is a sign of a novice<\/p>\n

AvgQtr = Sum(Jan, Feb, Mar) \/3<\/p>\n

is better<\/p>\n

AvgQtr = Mean(Jan,Feb, Mar)<\/p>\n

is what an intermediate programmer would do.<\/p>\n

2. You know options of options
\n3. You understand how the particular language you are using processes data.<\/strong><\/p>\n

For example, in SAS, let’s say you have two datasets<\/p>\n

Pretest has the following variables: Id Age Gender Testscore
\nWhere testscore is (obviously) the pretest score.
\nPosttest has the same variables: Id Age Gender Testscore
\nWhere testscore is (obviously) the posttest score.<\/p>\n

If you do this (bad!)<\/p>\n

Proc sort data = libref.pretest ;
\n\tBy id ;
\nProc sort data = libref.posttest ;
\n\tBy id ;
\nData libref.alltests ;
\n\tMerge libref.pretest libref.posttest ;
\n\tBy id ;
\n<\/code>
\nYou have just created a dataset that is a copy of posttest because the testscore from the second dataset named will copy over the first.<\/p>\n

Try this:<\/p>\n

Proc sort data = libref.pretest out = pre (rename = (testscore = pretest)) ;
\n\tBy id ;
\nProc sort data = libref.posttest out= post (rename = (testscore = posttest));
\n\tBy id ;
\nData libref.alltests ;
\n\tMerge pre post ;
\n\tBy id ;<\/code><\/p>\n

Yes, you COULD have done this by at least one data step where you renamed the testscore variable, but adding an extra step is inefficient.<\/p>\n

A good, short article on beyond the basics in proc sort was written by Kelsey Basset<\/a>.<\/p>\n

4. Use your knowledge of functions in your programming logic.
\n5. Don\u2019t forget about missing values.<\/strong><\/p>\n

For example, a researcher wants to categorize people who have ANY positive response to five questions on raising taxes, \u201cWould you vote to raise taxes if \u2026 the state budget isn\u2019t balanced?\u201d \u201cWould you raise taxes if \u2026 the option was to cut social services?\u201d and so on.<\/p>\n

A novice response would be:<\/p>\n

If q1 = 1 then taxes = 1 ;
\n Else If q2 = 1 then taxes = 1 ;
\n Else If q3 = 1 then taxes = 1 ;
\n Else If q4 = 1 then taxes = 1 ;
\n Else If q5 = 1 then taxes = 1 ;
\n\tElse taxes = 0 ;
\n<\/code>
\nBetter <\/p>\n

If sum(of q1 \u2013 q5) > 0 then taxes = 1 ;
\n\t\tElse if \tsum(of q1 \u2013 q5) = 0 then taxes = 0 ;<\/code><\/p>\n

The reason for having the second IF in there is that if you do not then all of those with missing values get set to zero, which may result in throwing off your results by a great deal, depending on how frequent missing data is.<\/p>\n

There are a variety of ways, some better some worse. However, one statement that does exactly what we want is :<\/p>\n

Taxes = Max(of q1 \u2013 q5) ;<\/code><\/p>\n

If any of the questions were answered 1, the value of taxes is 1. If all were answered 0, the value is 0 and if all were missing, the value is missing.<\/p>\n

I saw a similar example from SPSS on Douglas Smith’s page<\/a>. Although Recode is actually a command and not a function, my point is the same. Once you proceed from being a novice, you are naturally seeing the ways you can make your program more efficient.<\/p>\n

“Another example of using recode might be to invert the order of the values for a subjective evaluation variable. For instance, the variable \u201chappy\u201d has three valid response categories:<\/p>\n

1 = Very Happy
\n2= Pretty Happy
\n3 = Not Too Happy<\/p>\n

You might want to change the order to go from least happy to most happy. To do this, all you need to do is swap the values 1 and 3. The recode statement that will accomplish this is:<\/p>\n

recode happy (1=3) (3=1). <\/code><\/em><\/p>\n

Oh, and if you don’t use the command window, much less the Do-file editor in Stata, you are definitely a novice. Same goes for anyone who doesn’t write syntax for SPSS or hasn’t found a use for the Program window in SAS Enterprise Guide.<\/p>\n

That isn’t to say that there will never come a day when one can be considered a programmer by simply being very good at pointing and clicking.<\/p>\n

Just sayin’ …. today is not that day.<\/p>\n","protected":false},"excerpt":{"rendered":"

Writing a presentation for WUSS, I had to fill out the usual check box for the intended audience: Level of programming expertise: ___ Novice __ Intermediate __ Advanced and I started wondering when exactly does someone stop being a novice? One answer is that your programming no longer LOOKS like it was written by a…<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[9,8],"tags":[],"class_list":["post-570","post","type-post","status-publish","format-standard","hentry","category-software","category-technology"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/posts\/570","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/comments?post=570"}],"version-history":[{"count":4,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/posts\/570\/revisions"}],"predecessor-version":[{"id":575,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/posts\/570\/revisions\/575"}],"wp:attachment":[{"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/media?parent=570"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/categories?post=570"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/tags?post=570"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}