I must preface this with a disclaimer: my experience with persons from your ecosystem (based on the domain you shared) is limited to a number of persons I can count on one hand. I don’t intend to make this sound racist or assume a better-than-you stance.

Mainly about the admitting lack of knowledge or ability. I feel like this is a no-go and considered shameful in your ecosystem. I’ve worked with colleagues with this mindset a few years and it was usually troublesome to find out they were in way over their head and if they would’ve asked the team for feedback early, we as a team could’ve avoided some delays or bad infrastructure (code design) issues. It was a good learning experience for me, I now put my early drafts to team review to avoid exactly that situation.

This may sound old fashioned, but for learning the basics, I would stick to books instead of LLMs. Just because LLMs can state untruths with absolute confidence and because you are lacking the basics, you cannot spot that. Once you have good fundamentals learning from LLMs can be helpful but I would always request sources and check them. LLMs are not magic know-it-alls, they try to distill large amounts of text into small chunks and that process can be faulty. You are already on a good way here with you trying to sense when they give false information, but as I said, without solid fundamentals you might betray yourself with a false sense of safety here.

Your plan at teaching / guiding youth in technology is good, but as I said in an earlier comment teachers and guides should be very well versed in their field, otherwise they might teach untruths. And that hurts you twice, once because students will remember you teaching something wrong with confidence and it also might devalue everything else you taught. In the students mind, the thought “but what if that thing he/she said was also wrong?” will stick. For guidance, I would look up local hacker spaces, since they are keen on sharing their knowledge. At least here that’s the case.