Timeline for Ruby & OOP: FizzBuzz Game
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2017 at 9:38 | comment | added | Jonah | I don't say this to be mean, but it should be said because it's important that you know it: this code is comedically over-engineered. You really need to ask yourself why you would ever want something like this when you can write something like this | |
| Aug 5, 2017 at 22:52 | comment | added | Mark Thomas | I agree with Zack. This is a trivial problem and can be solved in one line of Ruby. The OO structure seems forced and a little too Java flavored. There's just no way to reason about the OO unless the problem gets a bit more sophisticated. Learning OO includes knowing when not to use it :) | |
| Aug 1, 2017 at 19:53 | answer | added | Zack | timeline score: 2 | |
| Aug 1, 2017 at 19:41 | history | edited | 200_success |
edited tags
|
|
| Aug 1, 2017 at 14:14 | history | edited | Ovidiu | CC BY-SA 3.0 |
added 52 characters in body
|
| Aug 1, 2017 at 13:10 | comment | added | Ovidiu | I want an object oriented approach, more than that not really. | |
| Aug 1, 2017 at 12:53 | comment | added | Mast♦ | Is there a reason you went for this specific approach? | |
| Aug 1, 2017 at 12:47 | review | First posts | |||
| Aug 1, 2017 at 13:57 | |||||
| Aug 1, 2017 at 12:42 | history | asked | Ovidiu | CC BY-SA 3.0 |