I am among those developers — as are important figures like Robert C Martin (aka Uncle Bob) or my university professor.

In bit parts of our industry this is also not only known but reality.

Just because you are unable to design projects like that (I assume, you never tried), doesnt mean, it has no value.

I argue you have probably never really worked with a valid architecture and there-for not even experienced its true value.

Khipu is a valid architecture, you can read about it here: https://betterprogramming.pub/meet-khipu-a-boilercode-free-implementation-of-clean-architecture-in-swift-f76ccab82ff3?sk=a8938450032cb5aa67a4e7938c0b774a

and

https://betterprogramming.pub/meet-khipu-a-boilercode-free-implementation-of-clean-architecture-in-swift-f76ccab82ff3?sk=a8938450032cb5aa67a4e7938c0b774a

Note, that my articles use prototyping UI just to proof it's viability — for real word projects you want to introduce an adapter or wrapper to get the full SwiftUI experince — but that is trivial. It isnt the scope of that articles.

You can also come to my talk at the "Declarative Amsterdam" conference next week, where I will demonstrate this by teaching the audience Khipu in a few minutes — because it doesnt take longer.

talk: "Declarative axiomatic and provable correct systems in Swift"

https://declarative.amsterdam/program

TLDR; if it is designed with an UI framework in mind, it isnt even an architecture.