Good article, interesting topic. I think this clock represents the layers of abstractions an application or piece of code goes through during its lifetime. At f

Good article, interesting topic. I think this clock represents the layers of abstractions an application or piece of code goes through during its lifetime. At first, no abstraction, just literal values. As you abstract the code you use the language as a tool to hide anything that repeats and expose only the essentials (a.k.a. abstracting). After DSL's at 9am in order to avoid getting back to hard coded values at 12pm, you HAVE to start abstracting at the conceptual/"business" level of the application. This would be the domain, however if the domain, when implemented, is causing a trip around the clock, this means the initial concepts are breaking the abstraction.