When I’m doing coding interviews I always like to start off and say I’m a big fan of very long variable names. “As descriptive as you can be” I say. Then I get to my first for loop. Instead of i I use “iterator” and then when I start a nested loop I use “jiterator” and it always gets a laugh.
I used to conduct coding interviews at my old job. If someone came in and had some humor like that, it would be big bonus points in my book. Being someone I would like to be on a team with is very important. Plus, I think it shows confidence and being comfortable in situations that make most people nervous.
I’ve been at two start ups and they had me interview people. Honestly this is what I looked for. I’d ask basic questions to prove you had an idea about coding, but I can teach someone to code, I can’t teach someone to be someone I like working with.
You can teach them to code if there is an underlying level of logic to build off. I’ve met a few people in life who I know for a fact will never code, no matter how smart they generally are.
This is absolutely essential and the reason my daughter started learning to code last year at 8. My dad got me into QBasic around the same age (we used X as an iterator back then btw) and ever since I’ve felt confident that I can work in any language given some time to familiarize myself with the syntax.
Functional languages notwithstanding. My instincts don’t apply to them. I get them, but my mind doesn’t flow with them the same way. Sometimes I wonder if there’s a way to expose my daughter to the concepts, but the applications tend to be heavy data processing and not fun games for kids.
When I’m doing coding interviews I always like to start off and say I’m a big fan of very long variable names. “As descriptive as you can be” I say. Then I get to my first for loop. Instead of i I use “iterator” and then when I start a nested loop I use “jiterator” and it always gets a laugh.
I used to conduct coding interviews at my old job. If someone came in and had some humor like that, it would be big bonus points in my book. Being someone I would like to be on a team with is very important. Plus, I think it shows confidence and being comfortable in situations that make most people nervous.
I’ve been at two start ups and they had me interview people. Honestly this is what I looked for. I’d ask basic questions to prove you had an idea about coding, but I can teach someone to code, I can’t teach someone to be someone I like working with.
You can teach them to code if there is an underlying level of logic to build off. I’ve met a few people in life who I know for a fact will never code, no matter how smart they generally are.
This is absolutely essential and the reason my daughter started learning to code last year at 8. My dad got me into QBasic around the same age (we used X as an iterator back then btw) and ever since I’ve felt confident that I can work in any language given some time to familiarize myself with the syntax.
Functional languages notwithstanding. My instincts don’t apply to them. I get them, but my mind doesn’t flow with them the same way. Sometimes I wonder if there’s a way to expose my daughter to the concepts, but the applications tend to be heavy data processing and not fun games for kids.
deleted by creator
And even if it didn’t help my chances directly like that, even getting a small chuckle would help me be more comfortable and confident.
Honestly finding someone who can relax and intergrate into your team culture is arguably more important that anything