Timeline for Abstract classes with static methods in PHP
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Dec 9, 2015 at 16:22 | history | suggested | superhero | CC BY-SA 3.0 |
Added a few resource links..
|
| Dec 9, 2015 at 16:11 | review | Suggested edits | |||
| S Dec 9, 2015 at 16:22 | |||||
| Dec 9, 2015 at 14:55 | comment | added | Andy | @GavinoGrifoni Sadly that happens in production. Sometimes you do not have the budget to do it all again correctly. Even for systems which are inherently wrong, if I end up adding a new module to that system, I do it the right way. So at least something is designed correctly. I recommend you to do the same. Use the ugly elephant, but make your baby beautiful. | |
| Dec 9, 2015 at 14:47 | comment | added | GavinoGrifoni | "if you must use them, your design is most likely wrong and needs refactoring" my exact thought here: I know that the development of this elephant took 2 years, so my suspect is they continued building over something without having a clear design done at the beginning | |
| Dec 9, 2015 at 14:44 | history | answered | Andy | CC BY-SA 3.0 |