lol yeah. My job is almost precisely like whatever the protagonist of every cyberpunk anything has before they become Neo/Hiro/whatever. It could not be more of a faceless cubicle farm if it tried. 95% of it is monotonous corporate drudgery.
So you're the asshole leaving all the dangling pointers?
UINT32 *)Address)*, I can't remember how it was written. He then asked me what the compiler would do with that loop. I told him nothing, it would read the memory 10 times. He argued with me that the compiler would flatten it out and store the memory value in the stack and just use that value 10 times. Here's the thing though, I know for certain the compiler included with the BIOS IDE they're using specifically doesn't do that. I've seen the assembly code for it, I know for a fact that it actually reads the memory 10 times. He argued with me and basically "lead me to water" by setting the variables as volatile. Just really annoying, he wasn't even on the team I was interviewing for.
Ohh boy! Standards.zzzz
Those are both braindead easy questions, what the fuck. Is that seriously the kind of questions they ask when you're interviewing for a programmer position. Fuck, I could be a programmer if that's the case.
For junior programmers literally anybody could probably do the work. I'm sure you could. (No sarcasm.)
They don't typically ask complicated problems, they just want to see if you know what you're talking about and if you can demonstrate how you think about things.
Well they way they phrase it doesn't help. Are you familiar with? That's a terrible way to ask a question. I'm familiar with how nuclear power plants work, but you wouldn't want me to have anything to do with them.
I was hands down the best programmer in all my Java classes, my Python class, and my various web development classes.
