Timeline for When does the "Do One Thing" paradigm become harmful?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 27, 2011 at 12:04 | comment | added | Michael Brown | Thanks for the comment. Note I'm not advocating premature abstraculation, just dividing logical operations so that it's easier to do so later. | |
| Nov 24, 2011 at 10:26 | comment | added | Yttrill | I upvoted this answer because I like the logic even though I disagree with it! Provide structure based on some complex thinking about what might happen in the future is counter productive. Factorise code when you need to. Do not abstract things until you need to. Modern code is plagued by people trying to slavishly follow rules instead of just writing code that works and adapting it reluctantly. Good programmers are lazy. | |
| Nov 24, 2011 at 1:33 | history | answered | Michael Brown | CC BY-SA 3.0 |