role of aesthetic in software design, development and education

## latchezar tomov ### link

“HCI is complicated, with radically differring languages and where communication can only exist within frames of come compromises”

• the market environment in which programmers exist

they relate aesthetics to motivation, expert knowledge, comprehensive comprehension (they call it overcoming the problem of induction), software reliability (cause maintainability)

they focus on intellectual aesthetics, the aesthetics of learning and education (example of geometry as beautiful logic for plato)

what is beautiful makes sense.

more rigor = more beauty??

the recurring phrase for aesthetics in science is simplicity and vastness

1. taste and style in coding (write code as lit)
2. aesthetic computing (the formal language itself is beautiful -> start from the language, then develop the software)
3. elegant software systems design (function follows form) - - systemic elegance is related to systemic complexity - - perceived elegance is related to hiding systemic complexity from the user (OOP, higher level languages have a higher perceived elegance)

the question they ask is: can we use aesthetic appreciation as a sign of knowledge?

aesthetic and science are linked through intuition, combining information and imagination when making purposeful decisions regarding meaning and pleasure

Furthermore, aesthetic appreciation is a sign of motivation for continuous improvement of both code and education – the quest for elegance is one for optimality, since in algebraic aesthetics beauty is recognized as perfection. Desire for beauty leads to striving for excellence. Aesthetic feeling is an intrinsic reward for programming efforts and can significantly accelerate goal-related learning and external reward intake

there is teaching beauty, and there is teaching beauty in relation to computer programs