W Lorenz, G. Wurzer:
"Programming for Architects; Version 2019";
Report for Bericht für Vienna UT, Digital Architecture and Planning; 2019; 74 pages.

As in a play, the name of the program already hints at its content (or: purpose). Likewise, the names used in a program should point at their role in the now beginning chain of events. Introducing proper names may be difficult at start. It requires a clear concept of what a program should do and in which steps it is going arrive at its solution. Architects often find it difficult to concentrate on the problem their program should solve, when all they want is really "a fancy solution" (Lawson: How Designers Think). But understanding the problem, breaking it up into sub-problems which are easily solvable and finally arriving at the solution is what lies at the heart of programming. To teach both knowledge about programming as well as a basic understanding on how to model and structure problems is what the book "Programming for Architects" is about. In this respect, the authors often deviate from this pure "programmer´s handbook" and relate to how algorithms we present work, and how they can be understood.

https://publik.tuwien.ac.at/files/publik_278693.pdf