Metaphors We Code By - Kevlin Henney

The world in which a software system lives is filled with meaning. The very act of development is an exercise in meaning - its discovery, its formulation, its communication. Domain-driven design makes this first class.
The abstract nature of software and its development leads to the extensive use of metaphors to confer meaning on the classes, functions, UI elements, relationships, patterns, etc., of our systems, as well as the mental models we hold about them and reason through.
But just because we are immersed in metaphor and meaning from an early age, and just because the daily work of software development employs metaphor and wrangles meaning, that doesn't mean we're necessarily good at it. Let's talk about the whats, whys and hows of metaphor, communication, naming and thinking.

[@JohnAzariah]

Some glorious puns in this talk, as you'd expect! And the unwarranted swipe against Australia was entirely superfluous! :D

[@marna_li]

The biggest challenge in software development is communication, or the lack of sufficient ones. Coders start coding without clarifying to others what they mean. Diagrams seem to be few, or left to the architect to make. Still that is just high-level and doesn’t capture the details. Developers thinking that the code is enough to explain what is happening.

[@MichaelPohoreski]

Amen! *Code documents HOW.* *Comments documents WHY.* Diagrams and external documents document WHY NOT. Sadly, these are never prioritized. :-(

[@mircdom4603]

nice one!