Towards better code snippets: Exploring how code snippet recall differs with programming experience

  • Michelle Ichinco
  • , Caitlin Kelleher

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

3 Scopus citations

Abstract

Programmers of all experience levels attempt to leverage code snippets with varying success, often as reminders or to learn new skills. To date, little work has explored the specific elements within code snippets that are challenging for novices. Comparing how novices and experts recall code snippets may expose what code elements programmers focus on and inform new approaches for improving examples for inexperienced programmers. We conducted a study, inspired by past novice-expert studies, in which we asked everyday, occasional, and non-programmers to study and then recall code snippets. The key distinctions and similarities in the types and locations of recalled tokens provide insight for a set of recommendations that could improve the presentation of code snippets.

Original languageEnglish
Title of host publicationProceedings - 2017 IEEE Symposium on Visual Languages and Human-Centric Computing, VL/HCC 2017
EditorsPeter Rodgers, Austin Z. Henley, Anita Sarma
PublisherIEEE Computer Society
Pages37-41
Number of pages5
ISBN (Electronic)9781538604434
DOIs
StatePublished - Nov 9 2017
Event2017 IEEE Symposium on Visual Languages and Human-Centric Computing, VL/HCC 2017 - Raleigh, United States
Duration: Oct 11 2017Oct 14 2017

Publication series

NameProceedings of IEEE Symposium on Visual Languages and Human-Centric Computing, VL/HCC
Volume2017-October
ISSN (Print)1943-6092
ISSN (Electronic)1943-6106

Conference

Conference2017 IEEE Symposium on Visual Languages and Human-Centric Computing, VL/HCC 2017
Country/TerritoryUnited States
CityRaleigh
Period10/11/1710/14/17

Fingerprint

Dive into the research topics of 'Towards better code snippets: Exploring how code snippet recall differs with programming experience'. Together they form a unique fingerprint.

Cite this