I was reading this article “Ten quick tips for teaching programming” by Neil C. C. Brown and Greg Wilson at https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5886386/ It had many useful suggestions one of which was “Don’t just Code” which I deciphered as: in addition to making students write code, we can also make them look at code and make meaning of it or engage with it in some way that gets them to think computationally. One way to do this they suggested was using Parsons Problems (That one is new to me). I quote them here:
For example, a growing number of educators are including Parsons Problems in their pedagogic repertoire [20, 27]. Rather than writing programs from scratch, learners are given the lines of code they need to solve a problem, but in jumbled order. Reordering them to solve the problem correctly allows them to concentrate on mastering control flow without having to devote mental energy to recalling syntax or the specifics of library functions. They are also liked by learners; Ericson et al.  found that learners were more likely to attempt Parsons Problems than nearby multiple choice questions in an e-book.
I looked up the researches referred to above as [20, 27]. The 20 reference at http://doi.acm.org/10.1145/2839509.2844617 validated and extended the original Parsons’ research at: http://dl.acm.org/citation.cfm?id=1151869.1151890
They implemented their Parsons Problems as web based drag and drop exercise. I get the general sense of how to create Parsons Problems. I want to use them. But I work in a part of the world where internet service is expensive and sometimes erratic. Similarly with electric power supply. So I wanted to design a paper based or some non-computer-based, physical media form of Parsons Problems that does not require use of electrical power or web access. I want to begin to use them in my lab/revision classes. However the logistics of their construction and use on non-computer media is not clear and/or problematic to me.
One option I considered was using flash cards with codes written on them for students to rearrange in the correct order of the code. One challenge with flash cards is the bulk. For example, consider an Intro Programming Class with students from several departments as high as 70 or more. Suppose you need a set of say 8 flash cards carrying the code for one program. For a class of 70 students, that would amount to producing 70 sets of 8 flash cards (i.e. 560 cards). Multiply this for say 300 some exercises for different topics and different programming subjects and you begin to see the challenge. There are resource constraints here. There is also problems of handling the bulk, and keeping the cards in good condition from one use to another etc.
Any ideas how one can produce non web-based Parsons Problems in some (preferably, physical/hard copy) form that is much cheaper, less bulky, durable and yet engaging for the students i.e. they don’t just write answers, they shuffle and move, and do some activity with the options?