Timeline for Are long methods always bad?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2019 at 19:09 | comment | added | gnasher729 | &sixtyfootersdude: It’s amazing how you know code that you have never seen and how to improve it. | |
| Oct 17, 2012 at 17:47 | comment | added | Loren Pechtel | @sixtyfootersdude: Sure, you could break it up. I didn't say it was impossible, I said there was nothing to be gained by breaking it up. While it wasn't 50 steps I've hit something like it: Creating a game world. #1 created the empty world, #2 created the terrain and then a whole bunch of steps after that massaged it in one way or another. | |
| Oct 17, 2012 at 16:17 | comment | added | sixtyfootersdude | The 50 step process can probably be summarized into several buckets through. Step 1 - 9 are parameter checks so create a new method called parameter checking. (I am sure there are some examples where this is not possible. I would be interested in seeing one). | |
| Oct 16, 2012 at 11:41 | history | made wiki | Post Made Community Wiki by Aniket Inge | ||
| Oct 15, 2012 at 22:52 | history | answered | Loren Pechtel | CC BY-SA 3.0 |