Separating Models from Implementation

[DavidIngram]

@yampeku

@birger.haarbrandt

this as an onion model

I’m assuming it is also in the sense that you cry more for each layer you remove

Separating Models from Implementation

Here’s another angle that complements yours. Assume you have lots of money, either as a gov org or as a tech company and you want to hire great staff. What’ll you do when engineers do not want to work with openEHR because it is such a big divergence from the safe career path? This is happening to us at all levels of hiring. Technical staff keep an eye on where they’re going from a tech-stack perspective, and they want to make sure what they’ll be working on will improve their prospects in the …

Tower of Babel (M. C. Escher)

In similar vein, this Escher version of the Tower of Babel is quite evocative of the stacks of Babel (babble? !) that become entrenched in shaky computational edifices. Best not to get too philosophical, here, but it is sometimes salutary to remind ourselves that limitations of languages are ages old, and are amplified, often out of sight, in the complexities of computational languages today.