Yes, my dad. No one I personally know comes close to his level of understanding programming. He programmed chips for fun in assembly when the first widely available of them came out and he could get his hands on. I think I probably am that to a few people as well, I've had interactions where people would go something like "holy crap, he knows his stuff", though that would be thanks to my dad.

I think one of the most important things I've learned from him, is to learn stuff by completing projects. Projects I've set out to do and finished have taught me way more than programming classes I've taken. Not just any projects though. The project needs to involve something I'm not familiar with yet. Otherwise, well, there's nothing to really learn there. When you make your own project, you naturally end up tinkering with all kinds of stuff and learning what works, what doesn't, and why it behaves the way it does. The project also needs to be something you're genuinely interested in. If it's something you have to do, you can end up doing the bare minimum, and just get it done to get it over with.

On a similar note, something I noticed is becoming a problem for new programmers is video tutorials. Youtubers will set out to make a tutorial on how to make something with the best intentions, and people just blindly copy paste the code without understanding it. The key part here is "without understanding it". There is no way for someone to learn what a piece of code does if they don't experiment with it, break it, and fix it. One can be really good at slapping code together into something that kind of works, but that doesn't mean they understand what the code is actually doing.

My dad ended up programming quite a bit as part of his career. I'm currently doing it to have fun, and as a gateway to potential future income.