Max's Reading List

From UIDWiki

Contents 1 On Deck 2 Notes 2.1 Crosby et al, The Roles Beacons Play in Comprehension for Novice and Expert Programmers 2.2 Lister et al, A Multi-National Study of Reading and Tracing Skills in Novice Programmers 2.3 Lister et al, Not Seeing the Forest for the Trees: Novice Programmers and the SOLO Taxonomy 2.4 MacLean et al, User-Tailorable Systems: Pressing the Issues with Buttons

On Deck

• Thomas and Thomasson, Scaffolding with Object Diagrams in 1st Year Programming Classes
• Davies, Display-based problem solving strategies in computer programming
• Check references 1,5,10,11,12,13,15 from Lister, Not Seeing the Forest for the Trees
• Something on where to store artifacts associated with code (in version control, elsewhere, etc.)

Notes

Crosby et al, The Roles Beacons Play in Comprehension for Novice and Expert Programmers

• Beacons: role-expressiveness of program; "typical indicator" of functionality

Lister et al, A Multi-National Study of Reading and Tracing Skills in Novice Programmers

• Doodles: position, number, trace, computation, synchronized trace; good students trace
• Mental models for programmers: schema, plan, template, idiom, pattern
• Mental simulation by experts?
• Careful walkthroughs vs. identifying schema/abstractions/etc. -- tension
• Study limited: array-heavy, non-idiomatic questions

Lister et al, Not Seeing the Forest for the Trees: Novice Programmers and the SOLO Taxonomy

• SOLO: prestructural, unistructural (understand some parts), multistructural (understand all parts), relational (integrates all parts)

MacLean et al, User-Tailorable Systems: Pressing the Issues with Buttons

• Worker, tinkerer, programmer; handyman
• Tailoring culture: worker expectations, feeling of ownership lead to asking and understanding, not just customizing themselves
• Active Property Engine (examine followup reference)
• Situated creation rather than programming by example/demonstration
• Shallow structuring: things a novice might need to use/modify near "surface" (here, buttons have parameters)
• "Tinkerers" can edit Lisp?
• Workers request "button to do X" where X shouldn't be done with a button, but "button" provides concrete way for need to be stated