News for hackers. Stuff that matters.
Re:How to Design Programs, Second Edition by amelius on Saturday August 05, 2017 @09:03AM (#14935489)
> First, the book discusses explicitly how programs should be constructed.

But is it right to assume and teach that there is only one way to do it? Aren't we continuously finding out new ways of constructing programs, and isn't it useful and fun to figure out new patterns while constructing new programs?

Re:How to Design Programs, Second Edition by open_bear on Saturday August 05, 2017 @10:07AM (#14935771)
Wirth said that program is a combination of data structures and algorithms in 1976, there were no _really_ new ways of constructing programs ever since.

HtDP teaches exactly that: proper construction of abstractions, small functions that operate over these abstractions and how to combine everything into a useful software.

Re:How to Design Programs, Second Edition by amelius on Saturday August 05, 2017 @12:21PM (#14936433)
So software engineering techniques such as React and Redux were already known back in 1976?

(Just an example)

Re:How to Design Programs, Second Edition by hex13 on Saturday August 05, 2017 @03:47PM (#14937529)
Redux for sure. Smalltalk had message based system like Redux has (with the difference that in smalltalk this system was object oriented). But functional programming also existed in 1976.