The concept of affordance was introduced by Donald Norman in his seminal book on usability “The Design of Everyday Things”. Affordances refer to parts of the design that point to the possibility of acting on them. Any design needs affordances, but when we aim for usability they need to clearly communicate their goal and way to use.
In this video we discuss the concept and how it applies to code design – that is to code structures -, rather than physical objects.
Links:
- https://www.theuncomfortable.com/#the-uncomfortable
- https://twitter.com/alexboly/status/1668127113856122880
- https://www.wikiwand.com/en/The_Design_of_Everyday_Things
- https://www.amazon.co.uk/dp/0465050654?linkCode=gs2&tag=useit-21
- https://careerfoundry.com/en/blog/ux-design/affordances-ux-design/
- https://www.geeksforgeeks.org/java-program-to-read-a-file-to-string/
- https://stackoverflow.com/questions/7729302/how-to-read-a-file-in-groovy-into-a-string
- https://github.com/davidsusu/regexbee
