[properbrew]

Love the writeup and I feel your pain, I'm a big fan of using LLMs for coding (as you'll see from my history).

> Still need to know when to step back and question your assumptions

Did you ever let the AI question your assumptions? I've found myself in a rut before and just giving it the issue with as little of my own personal context has helped surface what I need.

I'm curious how you found the bug in the first place? Was it during a vibe-code session or did you have a lightbulb moment?

Cool app btw.

[auspiv]

Thanks! How I eventually found it was stripping stuff back layer by layer. And by that I mean I started with the raw camera feed and got to where things worked well in a different swift view. And then from there, peeled stuff back from the main process feature by feature. And then bam, aircraft were exactly where they should be (minus the compass inaccuracy). I even had stuff like drawing mountain peaks (I live near Denver) as "aircraft" to figure things out, determining different FOV at different zoom levels (a lot of AI keyed in where the boxes would move in one direction at low zooms, be completely correct at some middle zoom, and then in the opposite direction at high zoom).

And that peeling back was me looking at each function to see what it did (I am a dev, but not for SwiftUI). So yep, can't vibe code it all!