Something contributing: No matter how bad teams fail — they are allowed to hire their own colleagues, leading to teams of inexperience developers hiring other inexperienced developers, simply because they dont understand what they are missing in experience.
I have seen teams burn several hundred thousands or literally millions of € on apps that an experienced developers could have delivered in a mere days or weeks — so less than 20K €.
Alan Kay calls this kind of development "Tinkering"-only, where-as an effective development needs math, engineering and science, too. Tinkering alone can only works for tiniest projects with no uncertainties.
https://www.youtube.com/watch?v=kgmAwnNxdgw
I created "Khipu", an architecture that follows engineering principles, and allows for scientific exploration of our problem domain scientifically (future part 2)
math is also covered, as all code path go through just a very small number of state altering statements ("Axioms") which are combined recursively to create the desired behaviour, much like in math itself. Khipu is written in Swift — where it shines brightest, due to swifts unique nested and annotated enumerations —, but the same declarative principles can be used in any languages with higher order functions — it wont create English (`.radio(.play(station:s))`)statements as in Khipu.
