Actually, I disagree. Do you not know the view update cycle in UIKit? The app launch cycle? How view controllers transition?

Understanding those behaviors are key to using UIKit effectively, and the equivalent is just as true in SwiftUI.

As the article points out, failure to understand such behavior can lead to sluggish, non-performant applications at best, and apps that crash, lose data, or have otherwise inconsistent behavior at worst.

There's more to programing than just coding to an interface.