What's wrong with this code?

[ShiftZ]

@jwatte

You should establish invariants that are as restrictive as possible (e g, “this is never NULL”) and then write your code assuming those variants, to make code that is as clean and well performing and easy to use as possible.

These should’ve been my words. Most poeple would not even see the amount of experience that is required to claim that simple thing.

@jwatte

If you’re testing “are these people familiar with working with the UE4 engine, where looking things up in source needs to be done at times” then that is a reasonable thing to do.

You have reaaons in your words. But my case definitely doesn’t fall under this explanation.

@jwatte

Or the job requires someone already familiar with “mobile development” and “unreal engine development,” because they are not looking to train someone up for this position.

I am familiar with both, but I’m not familiar with the document. Why would I? Each company uses their own styling guide. I can write in any style if it was described on a paper, even if I find it silly. It’s a matter of 30-60 minutes of reading. It can not be a subject of testing.