Continue GT Coding notes

notes

@@ -947,6 +947,53 @@ Initial coding questions:
 
 "Initial grounded theory coding can prompt you to see areas in which you lack needed data." (p.48)
 
+active coding -> use gerunds
+"We gain a strong sense of action and sequence with gerunds." (p.49)
+
+"If you ignore, gloss over, or leap beyond participants'
+meanings and actions, your grounded theory will likely reflect an outsider's,
+rather than an insider's view." (p.49)
+"Outsiders often import an alien professional lan-
+guage to describe the phenomenon." (p.49)
+
+"Make your codes fit the data
+you have rather than forcing the data to fit them." (p.49)
+
+To do while coding:
+"
+Remain open
+Stay close to the data
+Keep your codes simple and precise
+Construct short codes
+Preserve actions
+Compare data with data
+Move quickly through the data.
+"
+
+"Fresh data and line-by-line coding prompt you to remain open to the data
+and to see nuances in it"(p.50)
+
+Being critical:
+"Line-by-line coding frees you from becoming so immersed in your respon-
+dents' worldviews that you accept them without question. Then you fail to look
+at your data critically and analytically. Being critical about your data does not
+necessarily mean being critical of your research participants. Instead, being
+critical forces asking yourself questions about your data." (p. 51)
+
+in vivo codes: "codes of participants' special terms"(p.55)
+"useful analytic point of departure" (p.55)
+"preserve participants' meanings of their views and actions" (p.55)
+
+3 kinds of useful in vivo codes:
+"
+* Those general terms everyone 'knows' that flag condensed but significant
+meanings
+* A participant's innovative term that captures meanings or experience
+* Insider shorthand terms specific to a particular group that reflect their
+perspective.
+" (p.55)
+
+"Pursue telling terms" (p.57)
 ================================================================
 https://en.wikipedia.org/w/api.php?action=help&modules=main