Cheers for the answer! So would you think it would be wise to just ignore that for now and roll with my own intitution, and then after I am done just let someone do the quick code review?
What you can do is either just go ahead and write the game/engine and then look for advice, or come up with whatever ideas you think are reasonable and then post them here to get feedback before you start implementing it. This way you can get a better understanding of what the pros/cons of that approach are, plus you might be some additional insight into how you might do it better, before you commit to it and then find out it was tragically flawed.
And I agree that looking at source code is not that useful. What you need is some basic understanding of how things work and then you can use that to judge different approaches. You gain this by practice and experience, but some advice before you start can lead you to gain experience that's more valuable rather than possibly just getting frustrated.