Timeline for Clean Code / OOP on Monty Hall Simulation Implementation
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2019 at 21:25 | comment | added | Simon Forsberg | Just out of curiousity, will that code still follow? | |
| Feb 12, 2019 at 8:28 | history | edited | Pimgd | CC BY-SA 4.0 |
fix typo
|
| Feb 12, 2019 at 6:37 | vote | accept | Martin Frank | ||
| Feb 11, 2019 at 5:23 | comment | added | Martin Frank | @SimonForsberg that missing OO-Concept was my very reason to delete that question. After i postet my code i saw all these missing concepts, but i'm still glad you encouraged me to keep the question online. | |
| Feb 9, 2019 at 10:43 | comment | added | VLAZ | Not sure if it's worth bringing up but the simulation has a flaw in my eyes - an entirely new set of doors is created every time. That's not a code problem but a logic problem because it doesn't accurately reflect changing the choice. Given how it works right now, it seems better if it ran over the same door combinations first by changing choices, second without changing choices. Then you would get a more precise win percentage. Although both cases should be fairly close in what they report. | |
| Feb 8, 2019 at 18:00 | comment | added | Simon Forsberg |
I have a feeling that using a class for StraightPlayer, ChangePlayer and ShowMaster will be a bit overkill but it will be interesting to see what you come up with there. You have some other very good points here though.
|
|
| Feb 8, 2019 at 15:18 | history | answered | Roman | CC BY-SA 4.0 |