I'm pretty handy with the API, but the C behind it all feels pretty byzantine. I'm newish to OOP and C/C++ so before I can worry about interacting with systems

I'm pretty handy with the API, but the C behind it all feels pretty byzantine. I'm newish to OOP and C/C++ so before I can worry about interacting with systems like the window manager, internal database, depsgraph, renderers, RNA/DNA, etc. I gotta understand the paradigms that underpin its organization. Documentation is pretty light (but devs are very helpful in chat!). I guess Python has just spoiled me. I need a class and "everything is right there". In Blender's C/C++, functionality always seems spread across a variety of files and callbacks in a variety of folders. I tried to follow the main loop through an extremely simple action (select a cube onscreen) to see how the stuff I know happens, happens (draw orange outline, highlight in outliner, update undo history, etc.) I knew it would be a lot, but geez, even one of those things is like a week of reading through code. I do remember how intimidating Blender was the first time I used it though, vs how easy and natural it is now. I'm looking forward to when it will 'click' enough that I can find my way around even though I don't know how everything works. A 'core workflow' to trace through how stuff happens, if you will.