Re: Digital Twin applied to Software

Hi Andre,

> On Dec 4, 2022, at 3:41 AM, andre <[email protected]> wrote:
> 
…
> With Smalltalk, due to the ease of doing so, every developer is quick to add their own "system" and reinvent the wheel. Since the language is unable to enforce APIs and detect breaking changes at compile time, nobody dares to streamline and refactor away the bloat and redundancy, as it might break even more things. As a result, Smalltalk images are accumulating sleeping bugs, unclear APIs and conflicting assumptions.

In your team maybe :-). No effective team allows this to happen.  How? A few ways. 
- Insist that commits are reviewed by an experienced team member who is a domain expert on the region of the software in question
- pair inexperienced/nes developers with old hands
- when one finds duplication/inconsistency refactor it out
- periodically (once a quarter?) analyze the system looking for duplication/inconsistency/hurriedly-written-and-or-undocumented code snd *clean house*

If you don’t make room for this it is not Smalltalk’s fault, it is yours.  C++ does nothing to fix these issues either.

P.S. as an anal fascist anti-duplication refactorer I am open to mentor teams that need their code bases analyses and cleaned up ;-)