Dissertation references

These were cited in my dissertation and are listed here because they provide a handy summary of the work that I found helpful in conducting the dissertation study.

  • Abrams, B. (2008, March 17). Number of Types in the .NET Framework. Retrieved from http://blogs.msdn.com/b/brada/archive/2008/03/17/number-of-types-in-the-net-framework.aspx
  • Bailey, B. P., Adamczyk, P. D., Chang, T. Y., & Chilson, N. A. (2006). A framework for specifying and monitoring user tasks. Computers in Human Behavior, 22(4), 709–732.
  • Bailey, B. P., Konstan, J. A., & Carlis, J. V. (2000). Measuring the effects of interruptions on task performance in the user interface (Vol. 2, pp. 757–762). In the Proceedings of the 2000 IEEE International Conference on Systems, Man, and Cybernetics. IEEE.
  • Bannert, M. (2002). Managing cognitive load-recent trends in cognitive load theory. Learning and Instruction, 12(1), 139–146.
  • Barry, C. L., & Schamber, L. (1998). Users’ criteria for relevance evaluation: a cross-situational comparison. Information Processing & Management, 34(2), 219–236.
  • Bartell, A. L., & Spyridakis, J. H. (2012). Managing risk in internet-based survey research (pp. 1–6). In the Proceedings of the 2012 IEEE International Professional Communication Conference (IPCC). IEEE.
  • Bracht, G. H., & Glass, G. V. (1968). The external validity of experiments. American Educational Research Journal, 5(4), 437–474. http://doi.org/10.2307/1161993
  • Brandt, J., Dontcheva, M., Weskamp, M., & Klemmer, S. R. (2010). Example-centric programming: Integrating web search into the development environment (pp. 513–522). In the Proceedings of the SIGCHI Conference on Human Factors in Computing Systems. ACM.
  • Brandt, J., Guo, P. J., Lewenstein, J., Dontcheva, M., & Klemmer, S. R. (2009). Two studies of opportunistic programming: Interleaving web foraging, learning, and writing code (pp. 1589–1598). In the Proceedings of the SIGCHI Conference on Human Factors in Computing Systems. ACM.
  • Brandt, J., Guo, P. J., Lewenstein, J., & Klemmer, S. R. (2008). Opportunistic programming: How rapid ideation and prototyping occur in practice (pp. 1–5). In the Proceedings of the 4th International Workshop on End-User Software Engineering. ACM.
  • Carroll, J. M. (Ed.). (1998). Minimalism Beyond the Nurnberg Funnel. Cambridge, MA. MIT Press.
  • Clarke, S. (2003, November 24). Using the Cognitive Dimensions, Continued – Learning Style. Retrieved from http://blogs.msdn.com/stevencl/archive/2003/11/24/57079.aspx
  • Clarke, S. (2005). Describing and measuring api usability with the cognitive dimensions. In the Proceedings of the Cognitive Dimensions of Notations 10th Anniversary Workshop. Citeseer.
  • Clarke, S. (2007, February 7). What is an End User Software Engineer? Retrieved October 26, 2014, from http://drops.dagstuhl.de/opus/volltexte/2007/1080/
  • Cohen, J. (1988). Statistical Power Analysis for the Behavioral Sciences. L. Erlbaum Associates.
  • Cwalina, K., & Abrams, B. (2008). Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries. Addison-Wesley Professional.
  • DeMarco, T., & Lister, T. (2013). Peopleware: Productive Projects and Teams (3rd ed.). Upper Saddle River, NJ: Addison-Wesley Professional.
  • DeStefano, D., & LeFevre, J.-A. (2007). Cognitive load in hypertext reading: A review. Computers in Human Behavior, 23(3), 1616–1641.
  • Dillman, D. A., Smyth, J. D., & Christian, L. M. (2008). Internet, Mail, and Mixed-Mode Surveys: The Tailored Design Method (3rd ed.). Wiley.
  • Duffy, T. M., Curran, T. E., & Sass, D. (1983). Document design for technical job tasks: An evaluation. Human Factors: The Journal of the Human Factors and Ergonomics Society, 25(2), 143–160.
  • Henning, M. (2007). API design matters. Queue, 5(4), 24–36.
  • Knowles, M. S., Swanson, R. A., & Holton, E. F. I. (2011). The Adult Learner: The Definitive Classic in Adult Education and Human Resource Development (7th ed.). Taylor & Francis.
  • Ko, A. J., Myers, B. A., Coblenz, M. J., & Aung, H. H. (2006). An exploratory study of how developers seek, relate, and collect relevant information during software maintenance tasks. Software Engineering, IEEE Transactions on, 32(12), 971–987.
  • Krippendorff, K. H. (2012). Content Analysis: An Introduction to its Methodology (3rd ed.). Los Angeles ; London: SAGE Publications, Inc.
  • Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design, Revised and Updated: 125 Ways to Enhance Usability, Influence Perception, Increase Appeal, Make Better Design Decisions, and Teach through Design (2nd ed.). Rockport Publishers.
  • Lindeman, E. C. (1989). The Meaning of Adult Education (4th printing). Norman, OK: Printing Services, The University of Oklahoma.
  • Maalej, W., & Robillard, M. P. (2013). Patterns of knowledge in api reference documentation. IEEE Transactions on Software Engineering, 39(9), 1264–1282. doi:10.1109/TSE.2013.12
  • McGovern, G. (2006). Killer Web Content: Make the Sale, Deliver the Service, Build the Brand (1st ed.). London: A&C Black Trade.
  • Microsoft Corporation. (2014). Microsoft Manual of Style (4th ed., 3rd printing). Redmond, WA: Microsoft Press.
  • Microsoft Corporation Editorial Style Board. (2004). Microsoft Manual of Style for Technical Publications (3rd ed.). Redmond, WA. Microsoft Press.
  • Mihaly, F. (2011, November 1). Writing Helpful API Documentation. Retrieved from http://theamiableapi.com/2011/11/01/api-design-best-practice-write-helpful-documentation/
  • Mobrand, K. A., Cuddihy, E., Galore, E., & Spyridakis, J. H. (2007). The effect of structural cues on user comprehension, navigational behavior, and perceptions (pp. 1–7). In the Proceedings of the IEEE International Professional Communication Conference, IPCC 2007. IEEE.
  • Nykaza, J., Messinger, R., Boehme, F., Norman, C. L., Mace, M., & Gordon, M. (2002). What programmers really want: results of a needs assessment for SDK documentation. In the Proceedings of the 20th Annual International Conference on Computer Documentation (pp. 133–141). ACM.
  • Parnin, C. (2013, March 4). API Documentation – Why it Sucks [blog]. Retrieved November 2, 2014, from http://blog.ninlabs.com/2013/03/api-documentation/
  • Parnin, C., & Treude, C. (2011). Measuring api documentation on the web. In Measuring API Documentation on the Web (pp. 25–30). Waikiki, Honolulu, HI, USA: ACM.
  • Piaget, J. (1970). Science of education and the psychology of the child (First printing.). New York: Orion Press.
  • Pollock, E., Chandler, P., & Sweller, J. (2002). Assimilating complex information. Learning and Instruction, 12(1), 61–86.
  • ProgrammableWeb Research Center. (2014). Retrieved October 26, 2014, from http://www.programmableweb.com/api-research
  • Redish, J. (2012). Letting Go of the Words: Writing Web Content that Works (2nd ed.). Amsterdam ; Boston: Morgan Kaufmann.
  • Redish, J. C., Felker, D. B., & Rose, A. M. (1981). Evaluating the effects of document design principles. Information Design Journal, 2(3-4), 3–4.
  • Resig, J., 2008. Accuracy of JavaScript Time. John Resig. URL http://ejohn.org/blog/accuracy-of-javascript-time/ (accessed 3.7.15).
  • Reynolds, G. (2008). Presentation Zen: Simple Ideas on Presentation Design and Delivery (1st ed.). Berkeley, CA: New Riders.
  • Robillard, M. P. (2009). What makes apis hard to learn? Answers from developers. IEEE Software, 26(6), 27–34. IEEE.
  • Robillard, M. P., & DeLine, R. (2011). A field study of api learning obstacles. Empirical Software Engineering, 16(6), 703–732.
  • Robins, D., & Holmes, J. (2008). Aesthetics and credibility in web site design. Information Processing & Management, 44(1), 386–399.
  • Rouet, J.-F. (2006). The Skills of Document Use: From Text Comprehension to Web-Based Learning (1st ed.). Lawrence Erlbaum Associates.
  • Samuelson, P., & Scotchmer, S. (2002). The law and economics of reverse engineering. The Yale Law Journal, 111(7), 1575–1663. doi:10.2307/797533
  • Skinner, B. (1954). The science of learning and the art of teaching. Harvard Educational Review.
  • Sperber, D., & Wilson, D. (1986). Relevance: Communication and cognition. Oxford, U.K.: Basil Blackwell Ltd.
  • Spyridakis, J. H., Wei, C., Barrick, J., Cuddihy, E., & Maust, B. (2005). Internet-based research: Providing a foundation for web-design guidelines. IEEE Transactions on Professional Communication, 48(3), 242–260. IEEE.
  • Stylos, J., & Myers, B. A. (2005). How programmers use internet resources to aid programming. Submitted for Publication.
  • Stylos, J., & Myers, B. A. (2006). Mica: A web-search tool for finding api components and examples. In the Proceedings of the Visual Languages and Human-Centric Computing, 2006. VL/HCC 2006. IEEE Symposium on (pp. 195–202). IEEE.
  • Sweller, J. (1988). Cognitive load during problem solving: Effects on learning. Cognitive Science, 12(2), 257–285.
  • Tidwell, J. (2011). Designing Interfaces (2nd ed.). Sebastopol, CA: O’Reilly Media.
  • Tractinsky, N. (2004). A few notes on the study of beauty in HCI. Human–Computer Interaction, 19(4), 351–357.
  • Tractinsky, N., Cokhavi, A., Kirschenbaum, M., & Sharfi, T. (2006). Evaluating the consistency of immediate aesthetic perceptions of web pages. International Journal of Human-Computer Studies, 64(11), 1071–1083.
  • Tractinsky, N., Katz, A., & Ikar, D. (2000). What is beautiful is usable. Interacting with Computers, 13(2), 127–145.
  • Tuckman, B. W., & Harper, B. E. (2012). Conducting Educational Research (6th ed.). Rowman & Littlefield Publishers.
  • United States Department of Labor. (2014). May 2014 National Occupational Employment and Wage Estimates. Retrieved April 27, 2015, from http://www.bls.gov/oes/current/oes_nat.htm#15-0000
  •  Valcke, M. (2002). Cognitive load: Updating the theory? Learning and Instruction, 12(1), 147–154.
  • Van Schaik, P., & Ling, J. (2008). Modelling user experience with web sites: Usability, hedonic value, beauty and goodness. Interacting with Computers, 20(3), 419–432.
  • Van Schaik, P., & Ling, J. (2009). The role of context in perceptions of the aesthetics of web pages over time. International Journal of Human-Computer Studies, 67(1), 79–89.
  • Watson, R. B. (2012). Development and application of a heuristic to assess trends in api documentation. In the Proceedings of the 30th ACM international conference on Design of communication (pp. 295–302). Seattle, WA: ACM.
  • Watson, R., Stamnes, M., Jeannot-Schroeder, J., & Spyridakis, J. H. (2013). API documentation and software community values: A survey of open-source api documentation. In the Proceedings of the 31st ACM International Conference on Design of Communication (pp. 165–174). New York, NY, USA: ACM. doi:10.1145/2507065.2507076
  • Zakas, N.C., 2011. Timer Resolution in Browsers – NCZOnline. NCZOnline. URL http://www.nczonline.net/blog/2011/12/14/timer-resolution-in-browsers/ (accessed 3.7.15).