You are probably right that many tutorials and descriptions assume quite a lot of previous knowledge. Admittedly I've probably levelled a bit from the beginner programmer and Unity user by now but my general way of solving my own lack in skills is simply allowing for spectacular failure and/or boring results. In all (?) cases, my adventures into procedural generation stems from more or less explicit questions following the structure "What would happen if I did X?"
As an example, let's say I wanted to do random mesh generation in Unity. Reading some on it one learns that meshes are constructed from triangles. Well, how would it look if I on every frame just decided on a random number of triangles I wanted the mesh to have (e.g. between 1 and 10), and just made a Vector3[] verticies array 3 x number of triangles. And for each vertex I simply made a random Vector3, not caring at all about those rotation rules. Finally update the mesh with the new array.
That would probably be utter chaos, so maybe one could slow down the update frequency somehow or maybe one would only update some of the Vector3 in the array from the previous iteration and keep the rest.
It wouldn't be hard to get some results and see what happens when tweaking the parameters. Maybe hard to go from there to a full experience that could be called a game, but that is besides the point. In the process one learns some about procedural mesh generation and next time one can try to add more constraints and/or different sources or random. The procgen entity could be placed in a room on a pillar, drop a default FPS controller on the camera and you have an exhibition.
As for my song-writer, it is struggling with sounding human, but I don't mind:
"like forty miles a-a-away You crackin' Like ripples run everything
I've robbed a puddle.
Something something cooking inside of desire burning matches Lifting latches"