Once I build a DX11 driver it could become possible to apply it to rendering jobs too
About code commenting. It's true that having good variable and class names can do the trick. However, it's not the full solution. The problem comes when you write the functions. I learned that a good comment not only helps you remember whet the function does. But when you have a fellow programmer, both can be on the same wave. and you save time. So I comment code as I program, then I edit the comments to make it more professional.
At my university we mostly use a programming paradigm called 'Nominal Programming' or 'Design by Contract Programming', which requires you to write formally formatted comments with details about every single thing your function does and all conditions which have to be met when a function is called, you could even say that they pay more attention to the code comments than to the actual code
I pretty much hate this kind of programming though, comments are great, but nominal programming is not fool proof since it expects that the client using your code always gives perfectly correct input (so no exceptions or special case handling), causing crashes when faulty input is given (which is completely unacceptable in real-time systems)
Huge commenting also makes your code less manageable since most of the time you have to search where the comments end and where your actual function declaration starts
It's all about finding an ideal standard for commenting, don't over-do it but don't ignore it at all either
DONT GO THREAD HAPPY like Intel
