Status Updates From How to Design Programs: An ...

"But, the single most important advantage of abstraction is that it creates a SINGLE POINTnOF CONTROL for the functionality in a program. In other words, it (as much as possible) puts in one place the definitions related to some specific task." Pag 264

Course began on page 77, basically. #Go back later and run the code in the previous sections.#

«if students truly absorb the design recipe, they enhance their articulation skills more than anything else»—lol you guys suck at articulation skills.

In Sec “This Book and Its Parts” they claims that symbolic view of computation generalizes school algebra. For BSL & ISL ∃ https://docs.racket-lang.org/stepper/....

«Learning to design programs also means acquiring two kinds of universally useful skills. Program design certainly teaches the same analytical skills as mathematics, especially (pre)algebra and geometry. But, unlike mathematics, working with programs is an active approach to learning. Creating software provides immediate feedback and thus leads to exploration, experimentation, and self-evaluation.»

They say that separation of data manip from IO leads to MVC; indeed Elm natch leads to MVC-like arch. Hence I disagree w/ both Moldbug & Stephen Bond: FP is natch, IMHO it's just bigger power leads to giddy runaway abstraction, hence crazy Haskell libs & category theory.

«DrRacket supports highly playful, feedback-oriented learning with just two simple interactive panes: a definitions area, which contains function definitions, and an interactions area, which allows a programmer to ask for the evaluation of expressions that may refer to the definitions. In this context, it is as easy to explore “what if” scenarios as in a spreadsheet application[…]»—this is bad writing!