Timeline for How can wrapping an expression as a function be Clean Code?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 25, 2017 at 13:35 | comment | added | Frank Hileman | Dependency Injection again rears its ugly head. | |
| Apr 25, 2017 at 9:16 | vote | accept | imel96 | ||
| Apr 25, 2017 at 9:16 | comment | added | imel96 | @JacquesB thanks for clarifying that. Also just read someone said "Uncle Bob wrote thousands of pages on clean code. Kent Beck wrote for lines (rules)." Glad it's just common sense not some intricate conventions. | |
| Apr 21, 2017 at 15:37 | comment | added | JacquesB | @imel96: "Clean code" just means good, maintainable code. So if code is overly complicated then it is not clean. | |
| Apr 20, 2017 at 16:11 | comment | added | imel96 | My issue is how to answer the "clean code" argument. So, if it's over-complicated and YAGNI and not KISS then it's not "clean code"? Or should "clean code" comes after the other principles? | |
| Apr 19, 2017 at 15:01 | comment | added | user82096 | "Probably the developer have seen this design in a context where it makes sense"...or is just unthinkingly applying a rule that he learned in a book. There is a lot of that going on. | |
| Apr 19, 2017 at 14:40 | history | answered | JacquesB | CC BY-SA 3.0 |