Which is already defined in OCaml as: type 'a optional = Some of 'a | None Therefore it would be best to abstract this case as an Optional instead. So we can’t rely on empty String meaning no rule applied. Since we are working with abstract rules, we don’t know if one of them wants to output an empty String. Next! We have to think about that last empty String check. Let rec map l f = match l with | x:: xs -> (f x)::(map xs f)
let rec reduce l f a = match l with | x:: xs -> reduce xs f (f a x)
Here we go! Implementation Time!įirst! Since I don’t want to import any modules into my code I will implement two quite common functions: map and reduce. Which translates to if the input is divisible by 3 append “Fizz” to the output. Most programmers faced with this problem will write something along the lines of this (in Java of course): for ( int i = 1 i n % 3 = 0), " Fizz " So a basic game would go: 1 2 Fizz 4 Buzz Fizz 7 8 Fizz Buzz 11 Fizz 13 14 FizzBuzz 16 If none of these apply simply print out the number. The idea goes as follows: if a number is divisible by 3 then you print out “Fizz”, if it’s divisible by 5 “Buzz”, if it’s divisible by both: you guessed it “FizzBuzz”. So let’s take a look at one of the most simple problems: “FizzBuzz”. So please join me as I do exactly that! For fun! (Yes, I’m that bored.) FizzBuzz It’s that since we are getting basic problems, we tend to offer basic solutions that are dirty, complex and built to only work for these exact use cases.Īnd I would argue that in order to truly assess how good an engineer someone is, you’d have to see how good they can overengineer their solution to a problem.īecause, if you’re not already solving convoluted imaginary issues regarding reusability, maintenance, and scale in your head are you even solving the problem? Am I right? That terrifying moment when someone tells you a problem you haven’t heard of since your second semester of college and expects you to solve it quickly and correctly without autocomplete, Stack Overflow or a compiler.īut the main problem with the Coding Interview are not the conditions in which you have to work, or the judgment of your peers or any of that which we associate with stress, rejection and failure during an interview. If you’re ever looking for a job as a Developer, you will without a doubt encounter the “Coding Interview”.
FizzBuzz: How To Overengineer the Coding Interview
0 kommentar(er)
