You wouldn't torture him. You would just zero the probability of getting an offer. There's no SW house or colleague in his right mind that would want a developer that writes obfuscated and needlessly complex to understand code.
Unless they had, and i know this is hard to imagine in a c++ dev, a sense of humour
A way to torture an interviewer (C++, FizzBuzz)
41–50 of 84 posts
Re: A way to torture an interviewer (C++, FizzBuzz)
#42You wouldn't torture him. You would just zero the probability of getting an offer. There's no SW house or colleague in his right mind that would want a developer that writes obfuscated and needlessly complex to understand code.
I would not want developer to write this kind of code in production applications but I would very much hire a person who is capable of coming up with the code like this.
Re: A way to torture an interviewer (C++, FizzBuzz)
#43If a candidate were suggesting this as their serious FizzBuzz implementation fit for production, I'd have a hard talk with them about readability.
What implementation of FizzBuzz do you use in your production environment?
Re: A way to torture an interviewer (C++, FizzBuzz)
#44Earlier quoted context omitted.
I would not want developer to write this kind of code in production applications but I would very much hire a person who is capable of coming up with the code like this.
This whole point of Fizzbuzz is to see how one structures their code. Or at least ascertain that one _can_ write code in the first place.
Re: A way to torture an interviewer (C++, FizzBuzz)
#45I rather like this too - https://joelgrus.com/2016/05/23/fizz-buzz-in-tensorflow/
Re: A way to torture an interviewer (C++, FizzBuzz)
#46Earlier quoted context omitted.
This whole point of Fizzbuzz is to see how one structures their code. Or at least ascertain that one _can_ write code in the first place.
How much structure can a fizzbuzz have exactly?
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
Re: A way to torture an interviewer (C++, FizzBuzz)
#47Re: A way to torture an interviewer (C++, FizzBuzz)
#48Earlier quoted context omitted.
I would not want developer to write this kind of code in production applications but I would very much hire a person who is capable of coming up with the code like this.
This whole point of Fizzbuzz is to see how one structures their code. Or at least ascertain that one _can_ write code in the first place.
Re: A way to torture an interviewer (C++, FizzBuzz)
#49Earlier quoted context omitted.
What implementation of FizzBuzz do you use in your production environment?
Enterprise FizzBuzz, obviously https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
https://github.com/domdavis/fizzbuzz
"FizzBuzz split into a set of 4 microservices designed to be run as a fleet of docker images for highly concurrent, highly resilient deployment."
Re: A way to torture an interviewer (C++, FizzBuzz)
#50You wouldn't torture him. You would just zero the probability of getting an offer. There's no SW house or colleague in his right mind that would want a developer that writes obfuscated and needlessly complex to understand code.
While this code wouldn't be an instant offer, it would be a great solution in my eyes and it would follow hardest questions to qualify a candidate for senior position.
That's my opinion at least. I'm making a hiring decisions in my company.