If I may chime in here, since the introduction of Python as a native part of C4D, it is more than clear to me that learning Python by itself is not the main obstacle. What I got from people using C4D over the years: getting overwhelmed and lost finding the right parts in the SDK, and how to use or feed them with the proper information.
As Python was developed a while back in The Netherlands, as a language to teach kids to use coding options, the waste amount of recourses shouldn’t be duplicated and the real need comes as usual a little bit short.
From all the C4D specialized training I took from all over the place—one point stands out, the instructors go somehow magically to the “SDK place” and take what they need without any real uncertainty and without ever really leaving a clear explanation of the logic one must apply to use it. I used training in several languages—same result in each.
To create a plug-in or a single specialized solution is not working, if the way to the library is not well explained. This needs to come first - nothing else makes sense for my before that,
Just my two cents.
I look forward to a well document format and procedure series about the SDK.