EUDability: a new construct at the intersection of end-user development and computational thinking [I don't know why it was so hard for me to wade through this paper, despite being squarely in my interests. I feel the academic format is a poor match for the content which could be a good blog post?] The goal is extending "usability" so "use" includes end-user programming. ... They observe that "computational thinking" skills become a "literacy" when practiced, including the experience of when to apply which skill. [by that stage the paper still feels like a lot of word shuffling]... The real stuff only comes in pp. 25–27 where they identify qualities ("dimensions") by which the software can _help users apply those computational skills_: • _Concreteness_: this dimension refers to the capability of a EUD environment of presenting concepts and requests in a concrete way, without requiring the user highly-developed abstraction skills; • _Modularity_: this dimension regards the availability in a EUD environment of different elements, blocks, modules or similar things, which help end-user developers decompose a problem and identify the pieces that may compose its solution; • _Structuredness_: when a EUD environment supports the structuring of a solution in a step-by-step process and facilitates the connections between the input and output of the different steps, it can be considered as having the structuredness property; • _Reusability_: when the outcome of a EUD activity can be reused in other situations and possibly shared among different end-user developers, the EUD environment possesses the reusability property; • _Testability_: this dimension refers to the capability of testing the outcome of the EUD activity within the EUD environment. and the payoff is this diagram where everything falls neatly in place: