I got where I am, knowledge-wise, by annoying the sh*t out of the people in ##c+±general on Freenode IRC and now C++Help on Discord lol And eventually, being able to understand what was being discussed in CppCon and ADC videos on youtube.
I agree, there’s partly the problem of “I worked super hard to figure this stuff out myself, why would I give it away for free” mentality that’s prominent with self-taught folks, but there’s also the part of “this c++ stuff isn’t easy”! If it were, it would be taught alongside math, english, and social studies in elementary school.
It’s never really stated anywhere that we should use git to get set up with JUCE, until you start working or collaborating with other programmers, and then it’s like, “do you know how to use git?”. If you answer ‘no’, you get a pretty quick explanation of how to use it, and then when you go snoop around on the JUCE forum and see where all the bug fixes get reported, you’ll immediately “get” all of the “fixed with commit a4d5e23s” posts and wish you had learned about git source management before you even learned how to program a single line of code. At least, that’s what my experience was. The ability to roll back is such a life-saver sometimes.
I wouldn’t beat yourself up about not realizing that you should have been cloning the repo from Github and just pulling/recompiling ProJucer whenever there is a new update. I’ve been working on a ‘Programming for Musicians’ youtube series, to kind of pave the way for TheAudioProgrammer’s videos, and the very first video is literally How to take a blank machine, install an IDE (xcode or visual studio), clone the JUCE repo via command line, Build Projucer, make a GUI project in Projucer, and finally, build it in the IDE.