Going to take a stab at defining measuring sticks for the problem: Here's some metrics we should measure a "system for programming education," of whatever form

Going to take a stab at defining measuring sticks for the problem: Here's some metrics we should measure a "system for programming education," of whatever form, against. --Success is measured against new students with zero programming background. Todo would be defining zero programming background. Ideally people who've never evaluated a statement before AND never used a CLI interface AND without an amazing mathematical background. --Students do not feel regret, unhappiness or anxiety before they start or after they finish a 1-2 hour programming session. Students want to program in the future. All other things being equal. --The level of expertise to target for a "solid programmer" is creating discrete systems using higher order abstractions from scratch. Whilst using a strong mental model of what higher order abstractions actually look like in their physical state to improve their creations. A secondary KPI might be "can the student make a compiler." But a mental model of what higher order abstractions actually look like in logical state seems like a good goal. --Currently underrepresented cultural backgrounds show end state success at the same rate as other cultural backgrounds, all other things being equal. Programming stuff is difficult, when there are difficult academic barriers to overcome people on the south side of social inequality fail more. Thus it needs to be a metric. --Could possibly program for money?.