Loose convention - upper camel casing - for constant values.

Hi,

I think that is very minor detail in general.

As you can see in video, he is creating private struct inside of the class. He want's to store how high is the cell in table, but avoid using magic numbers.

So in my opinion he's using this loose convention to differ constants that really only hold some specific number, having it properly named and wrapped.

It is static to be accessible even when object is not yet ready (or initialized), so it can be used always.

Back in old days with C code something similar was used, but it was in all capitals and preprocessor directives were used. For example you had like:

#define DEFAULT_X_RESOLUTION 800
#define DEFAULT_Y_RESOLUTION 600

or even better: true or false;

#define TRUE 1
#define FALSE 0

because there was no explicit bool type in C.

It was also loose convention, but clearly visible in code, as intended.

I hope that helps!

BR, Jarek