Nice bit of synchronicity! I've also been looking into Residuality theory in the past weeks, although I hadn't understood it as well as your article puts it.
The simple examples really help to get over the "scientific jargon".
It really is striking how simple the process is, it defies belief even.
Btw, Barry has written a book about this topic, it's called Residues: Time, Change, and Uncertainty in Software Architecture and you can find it in https://leanpub.com/residuality
PS: Agree with you about the name - "residue" is atrocious ;)
Nice bit of synchronicity! I've also been looking into Residuality theory in the past weeks, although I hadn't understood it as well as your article puts it.
The simple examples really help to get over the "scientific jargon".
It really is striking how simple the process is, it defies belief even.
Btw, Barry has written a book about this topic, it's called Residues: Time, Change, and Uncertainty in Software Architecture and you can find it in https://leanpub.com/residuality
PS: Agree with you about the name - "residue" is atrocious ;)