Like most other things related to the eventual dissertation I’ll have to write, “coding” was a vague, fairly upsetting concept I kind of didn’t want to talk about. After the coding exercise in class, I realized I’ve already done it in some form before this. As an undergraduate, I completed an honors thesis, and I actually did a fair amount of coding for that project. None of it was as structured as the coding discussed in class; it was mainly through color-coded notations in margins of books and print outs; and I certainly didn’t call it coding. However, it served the same basic function: condensing and organizing ideas and concepts into larger groups that can be better analyzed. Having realized this, I am less worried about the coding in my dissertating future.
By nature, I’m a hyper-organized person who makes massive amounts of notes on almost everything–including leisure reading–so I think coding will end up being an enjoyable process for me. Of course, it is always possible it will end up driving me out of my skull, but at least I will begin the process expecting to enjoy it. This type of coding appeals to me in that it bases conclusions on the data and actual situation rather than allowing for preconceived notions to take over the analysis.
I could certainly see the need for another coder to check one’s notes though. My partner in the coding exercise caught a lot of the same things I did but also managed to note multiple items I either didn’t note or didn’t notice.