Ouch, sorry to hear that. Oftentimes university classes are more about giving a theoretical background instead of hands on practice. The theory is useful, espec

Ouch, sorry to hear that. Oftentimes university classes are more about giving a theoretical background instead of hands on practice. The theory is useful, especially if one is trying to write performant code, but it's a big wall to scale before being able to play. Not everything needs to be optimized to the maximum these days, with computers being so fast, and oftentimes inefficient code is fine for just playing around. In your example of graphics APIs, the barrier to entry has gotten much higher with programmable GPUs if one wants to use APIs such as OpenGL, D3D, or Vulkan. It used to be that one could just draw polygons on the screen with C code that would fit in a single page using GLFW, OpenGL immediate mode, and the fixed function pipeline. Hilariously enough, you can see the difference between the deprecated immediate mode API (8 function calls) and the "recommended" way on this Stack overflow answer (fragment and vertex shaders, a few buffers, and way more code): https://stackoverflow.com/questions/6733934/what-does-immediate-mode-mean-in-opengl https://stackoverflow.com/questions/6733934/what-does-immedi... On the other hand, if all you want is to draw things for fun and you're not trying to write a AAA video game, a scene graph-style API or interactive environments like processing are much better fits, as you point out.