Some random ideas that might help
Start by making sounds - even simple ones. A few UGens or functions at a time, and start playing with them. This is much more engaging than reading specific documentation, and you will learn a lot about the métier. It’s not just computations; what we do has much more to do with connecting the brain and the ear, playfully, skillfully coping with a few things at a time. Never forget.
Pick small projects rather than trying to learn “everything.”
Use the “copy-modify-create” approach. Copy code from documentation and small programs online and start from there. Play with the code. Many times, you will grasp what each part does and, equally important, how it connects with sound.
Keep a personal collection of snippets that you understand and use. This will prevent you from going to the documentation and losing yourself there. Most of the documentation in our field does not teach much about programming; it is all pretty confusing. Trying to “learn” programming reading max, pd, or sc documentation wastes time. – This is not even controversial; the sc documentation tells the reader to learn about OOP elsewhere, a programming language very close to Smalltalk. Go figures…
But remember, read this with a grain of salt. There is no correct or wrong way to learn programming; there are, in fact, different programming cultures and not much to compare. Maybe you will learn a lot connecting your brain and ears playing around with supercollider, and you can also have fun learning about computability/programming. But it does not mean they are the same, or you need one to do the other.
Take breaks when you feel overwhelmed. SuperCollider will still be there when you come back. And remember, everything will feel completely different when you have a “music vision” in your head. In my experience, I would not have learned about music, sound, and computation in the same way if I had not also been performing live and writing music for other people to play. See the computer as part of all of this experience.