Subverting the software interview (2021)
1–10 of 80 posts
Re: Subverting the software interview (2021)
#2Probably didn't pass the interview. The implementation was rather simplistic and low quality.
Here's a better enterprise version: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
Though the fact that it was written some years ago might be a weakness. Some interviewers might prefere a more modern, distributed solution.
Re: Subverting the software interview (2021)
#3So good.
Re: Subverting the software interview (2021)
#4[deleted]
Re: Subverting the software interview (2021)
#5great read. entertaining and engaging, wonderful creative writing with nerd flair.
Re: Subverting the software interview (2021)
#6I'm smiling as I read from top to bottom.
Re: Subverting the software interview (2021)
#7Great writing, hilarious.
I feel like we all could know someone who fits these characteristics.
Re: Subverting the software interview (2021)
#8Everything makes sense to me until the Dual definitions:
newtype Dual a = Dual {getDual :: a}
instance Semigroup s => Dual s where
(Dual a Dual b) = Dual (b a)
instance Monoid m => Dual m where
mempty = Dual (mempty)
These are declaring instances of Dual, but they are providing method definitions for Semigroup and Monoid as if they were declaring instances for those types. I plugged this into ghc and I couldn't get this to compile either way. This isn't using an extension or some more obscure language than haskell is it?Re: Subverting the software interview (2021)
#9Another in this genre: https://aphyr.com/posts/342-typing-the-technical-interview
Re: Subverting the software interview (2021)
#10Great writing, hilarious. I feel like we all could know someone who fits these characteristics.
I worked with a guy who implemented map and reduce in C++ as a subtask of some other task. It was, of course, a header-only templated monstrosity.
He called it "fun.hpp".
"Fun" times, indeed, working with him.