{"id":23643,"date":"2008-01-30T10:00:01","date_gmt":"2008-01-30T10:00:01","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/oldnewthing\/2008\/01\/30\/even-without-a-nitpickers-corner-i-have-to-worry-about-nitpickers\/"},"modified":"2008-01-30T10:00:01","modified_gmt":"2008-01-30T10:00:01","slug":"even-without-a-nitpickers-corner-i-have-to-worry-about-nitpickers","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20080130-01\/?p=23643","title":{"rendered":"Even without a nitpicker's corner, I have to worry about nitpickers"},"content":{"rendered":"

Even without a nitpicker’s corner, I have to worry about nitpickers. I just have to do it in a more subtle way.\n Here are some examples of changes I’ve made to upcoming entries in order to forestall nitpicking:<\/p>\n\n\n\n\n\n\n\n\n\n
Original text<\/th>\nRevised text<\/th>\nReason<\/th>\n<\/tr>\n
… entries in our list… <\/td>\n … entries in our table<\/font>… <\/td>\n The entries are kept in an array, but writing “list” may cause some people to nitpick that an array is not a list. <\/td>\n<\/tr>\n
… this function returns X… <\/td>\n … this function can be asked to<\/font> return X… <\/td>\n The function returns different things based on what the caller requests, but the only case we’re interested in right now is the case of X. <\/td>\n<\/tr>\n
… X affects only Y. <\/td>\n … X typically<\/font> affects only Y. <\/td>\n Again, I have to add the qualifier to protect against the case where a program intentionally broadens the scope of X. <\/td>\n<\/tr>\n
… X isn’t a problem because… <\/td>\n … X isn’t usually<\/font> a problem because… <\/td>\n There can be cases where X is a problem because the program explicitly created the problem for itself, so I have to put in a qualifier. Indeed, later in the article I give an example of how a program can cause this problem, so I’d better leave myself some wiggle room at the expense of rhetorical power. <\/td>\n<\/tr>\n
… a holiday…. <\/td>\n … a holiday in the United States<\/font>… <\/td>\n Otherwise somebody would make some smart-alec remark like “It’s not a holiday where I live.” [Typo fixed: 10am] <\/td>\n<\/tr>\n
… the kernel …. <\/td>\n … the exception dispatch code<\/font>… <\/td>\n To avoid confusion between “the kernel” and “kernel mode”. <\/td>\n<\/tr>\n
… 64KB … <\/td>\n … about<\/font> 64KB… <\/td>\n Because the limit is actually 65280 bytes<\/a>. <\/td>\n<\/tr>\n<\/table>\n

What’s scary is that I’ve noticed that I begun pre-emptively nitpicking my own entries while I’m writing them<\/i>. In the balance between writing something that reads more naturally and something that is more resiliant to nitpicking, I’ve unfortunately started preferring the latter.\n Observant readers may have noticed that I’ve slowly introduced a section called “Pre-emptive snarky comment” wherein I try to anticipate drive-by “Hey wouldn’t it be hilarious if I ridiculed Microsoft on a Microsoft employee’s blog?” comments. It seems to be largely successful, although sometimes people will post the identical snarky comment that I pre-empted<\/i>. These are probably the people who talk just to enjoy the sound of their own voice.\n An extension of this is the “Now that you brought up something that sucks, I’m going to tell you that it sucks” phenomenon. This is pretty much guaranteed whenever I bring up anything that is related to UAC and security, since it appears that everybody agrees that UAC sucks, so any blog entry that talks about elevation invariably leads to comments about how UAC<\/a> sucks<\/a>. There are also popular tangents, such as any article that mentions installing software turning into a “post your complaints about setup here<\/a>” thread.\n Some people are more indiscriminate and merely bash Vista<\/a> whenever they get a chance, such as using a story about the psychology of how people fail to process information that they see to rant about how it’s hard to copy text out of the event viewer<\/a>.\n (That article about how people fail to process information that they see was indeed an unmitigated disaster. Everybody got into arguing over how the message should have been presented so the user would be more likely to see it, but that completely misses the point. The user positively confirmed, “I see the yellow warning.” The problem wasn’t that the user didn’t see the message; the response confirmed that the user saw the message just fine. What the user didn’t do was process<\/i> the information. It’s my fault for choosing a bad title. Instead of “People can’t see things that are right in front of them,” I should have titled it “People see things but don’t pay attention to them,” opting for precision even though it meant I couldn’t use the idiomatic phrase can’t see what’s right in front of you<\/i>. What made it worse is that I fell for the trap<\/i>. I responded to the details instead of saying, “Whether your suggestion would have helped the user see the message or not is totally irrelevant to the point of the article.”)<\/p>\n

I also hadn’t predicted that my discussion of how reasonable people can disagree about how a setting should be exposed<\/a> would turn into a discussion of how to shut down your computer, turning a footnote into the primary topic of discussion. But that’s a fairly common occurrence: People focus on a side detail (which I added for color) and ignore the point of the story. Sometimes I think I’d be better off if I didn’t give examples. That way nobody could be distracted by them. <\/p>\n","protected":false},"excerpt":{"rendered":"

Even without a nitpicker’s corner, I have to worry about nitpickers. I just have to do it in a more subtle way. Here are some examples of changes I’ve made to upcoming entries in order to forestall nitpicking: Original text Revised text Reason … entries in our list… … entries in our table… The entries […]<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[103],"class_list":["post-23643","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-non-computer"],"acf":[],"blog_post_summary":"

Even without a nitpicker’s corner, I have to worry about nitpickers. I just have to do it in a more subtle way. Here are some examples of changes I’ve made to upcoming entries in order to forestall nitpicking: Original text Revised text Reason … entries in our list… … entries in our table… The entries […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/23643","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=23643"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/23643\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=23643"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=23643"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=23643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}