Keeping Perspective

In the last post, I discussed my efforts to impose greater structure on my code system. In doing so coding has become an easier process in two ways. First, I have a better understanding of my themes which allows me to understand when to apply a certain code. By having a greater understanding of how I am defining codes I can recognize themes faster and apply codes with greater confidence. The second aspect is concerned with my outlook on the project and the process. I find myself enjoying the process more, mainly because I have replaced the confusion that stemmed from my unstructured codes with greater clarity and confidence. I am still struggling with some aspects of my code system. It can be tough to decide how to code certain lines of text. At times this can be remedied by applying multiple codes, but at other times applying multiple codes is not appropriate and I have to deeply think about what code to assign. This leads to an important point about coding and analysis, be sure to take time to think about the “big picture” of your work. Often when I run into issues it helps to take a step back and think about how this code relates to others and fits into the project as a whole. On the surface, this idea sounds simple and apparent. However, I often find when I spend multiple hours coding, I will focus on small portions of text for long periods of time which can be a useful mindset, but it can also mean I lose track of the text segment in relation to the scope of my project. Taking breaks periodically to think about how this code fits into a theme which fits into my project as a whole can be a useful exercise. As I continue my work, I need to remind myself to periodically stop and think. No computer, just time to think. Of course, after a brainstorming session, it is important to record your thoughts so you can revisit them and build on these ideas.