SRA

I have spent years trying to understand and follow established software architectures - and wound up writing my own at the end: SRA (Specification - Realization - Assembly). Please do check it out and let me know what you think!Background:Whenever I would learn a new architecture, the initial ideas seemed interesting but the implementation almost always ended up with my autistic sense of detail screaming loudly about one or more shortcomings and even inconsistencies.For example, a lot of architectures rely on human discipline, give certain aspects of the software - such as the UI - an unproportional amount of power, or promote coupling despite claiming otherwise.As a programming generalist, I also found certain architectures hard to transfer between platforms and project types, especially in multiplatform code bases.In the end I started from the basics; What is good code? What principles are common regardless of language? How can we make good code easier to write than bad code? What makes code adaptable to evolving technology and changing requirements?The result: SRA. Enjoy!