Live data from Hacker News

A way to torture an interviewer (C++, FizzBuzz)

news.ycombinator.com

41–50 of 84 posts

Re: A way to torture an interviewer (C++, FizzBuzz)

#41

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

I mean the code also includes a bunch of undefined behaviors, we do not joke about that

Re: A way to torture an interviewer (C++, FizzBuzz)

#42
post #35

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.

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)

#43
post #2

If 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?

we just hardcoded the solutions for 1 to 100 manually. It's been fine so far.

Re: A way to torture an interviewer (C++, FizzBuzz)

#44
post #35

Earlier 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.

How much structure can a fizzbuzz have exactly?

Re: A way to torture an interviewer (C++, FizzBuzz)

#45

I rather like this too - https://joelgrus.com/2016/05/23/fizz-buzz-in-tensorflow/

I always felt that being annoying is an art - something that requires dedication and craftsmanship - and whoever wrote (and hopefully actually did) this is clearly a master at it.

Re: A way to torture an interviewer (C++, FizzBuzz)

#46
post #44

Earlier 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?

How much structure would you like?

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Re: A way to torture an interviewer (C++, FizzBuzz)

#48
post #35

Earlier 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.

I could not care less about the purpose of FizzBuzz. In my other life I've interviewed many programmers and I did not get disappointed. But I would never ask them to do live coding in a first place.

Re: A way to torture an interviewer (C++, FizzBuzz)

#49

Earlier quoted context omitted.

What implementation of FizzBuzz do you use in your production environment?

Enterprise FizzBuzz, obviously https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

No microservices, not nearly Enterprish enough:

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)

#50

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.

Fizzbuzz is a pass to the next questions. It's a way to weed out random people who have no idea about programming but for some reason came to the interview.

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.

Post reply on HN