Timeline for Interview coding test: Fizz Buzz
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 30, 2016 at 6:57 | comment | added | Benjamin Gruenbaum | This is still an overkill super complicated FizzBuzz and for what it's worth I would fail someone a coding interview for that. | |
| Apr 29, 2016 at 21:32 | comment | added | Software Engineer | I mentioned in another comment, but should put into the post, that the duplication isn't real -- it's an artefact of showing how the code has evolved across the three requirements I had to implement, and that in reality I'd only have the third function. I can see clearly now that this is a mistake and confusing. | |
| Apr 29, 2016 at 16:02 | history | notice removed | Simon Forsberg | ||
| Apr 29, 2016 at 15:29 | history | edited | OldCurmudgeon | CC BY-SA 3.0 | added 562 characters in body |
| Apr 29, 2016 at 14:21 | history | notice added | Simon Forsberg | Insufficient justification | |
| Apr 29, 2016 at 13:33 | comment | added | David K | Or maybe better, omit them altogether and let the caller decide what separators to use. And yeah, I know it's a pretty small nit to pick. | |
| Apr 29, 2016 at 13:22 | review | Low quality posts | |||
| Apr 29, 2016 at 14:21 | |||||
| Apr 29, 2016 at 13:21 | comment | added | OldCurmudgeon | @DavidK - That can be fixed by moving the .append(" ");s around. | |
| Apr 29, 2016 at 13:18 | comment | added | David K | What does encode return when n is 15? I think the usual spec for a FizzBuzz problem is it's supposed to return a compound word like "FizzBuzz" (no spaces between "Fizz" and "Buzz"). | |
| Apr 29, 2016 at 10:44 | history | answered | OldCurmudgeon | CC BY-SA 3.0 |