Warning, some spoilers ... I don't like this kind of tests. I always stumble upon questions where I wonder if it's a trick question or just a typo/mistake by t

Warning, some spoilers ... I don't like this kind of tests. I always stumble upon questions where I wonder if it's a trick question or just a typo/mistake by the test creator. Example: Function D will loop for ever if size_t is an unsigned type. Function E won't even compile because of the comma and the missing * in the first line. Function C is an edge case. The external effect is the same only in a single threaded environment. If there's parallelism or interrupts the external effect might not be the same for certain conditions. So what do I do? Do I check the box or not? If I do, it might fire back because "I didn't catch those obvious errors". If I don't then my application might fall through the grid because "too many wrong checkmarks". Maybe the recruiter is just a mindless HR bot and doesn't understand any of these questions. So arguing would be pointless. If you want to determine my skills, give me something to do. Say give me 6 hours to implement a server or something (not too big, not too small for 6 hours), then shuffle through my code and see if its quality pleases you. Being bombarded with off-by-one trick questions just annoys me.