Timeline for Modularity vs Single class simplicity
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 19, 2017 at 19:31 | comment | added | iteratingself | It's this as an opportunity to try and understand what makes code good or bad. Look past best practices and develop a deeper understanding. Then you can verbalize that understanding and better argue for what you think it's right. | |
| Mar 9, 2012 at 5:31 | comment | added | arunmur | @kevincline The code is in general many times shorter and its functionality is much clearer with simple well defined interfaces. Having even a single pattern makes the code look a bit more complicated than a single class, cause now some functionality is exported off to another class. Making them open 2 files. But the subsystems are kept simple, coherent and rarely has had any bugs till day. I guess the extra effort to learn the subsystem to extend it makes them kinda cringe. They dont see the benefits it has bought but only the pain of sticking to a system. | |
| Mar 8, 2012 at 18:43 | comment | added | kevin cline | Is the new code shorter? If not, then they have a legitimate complaint. If it is, then why aren't they happy? | |
| Mar 8, 2012 at 18:01 | answer | added | RalphChapin | timeline score: 0 | |
| Mar 8, 2012 at 10:59 | vote | accept | arunmur | ||
| Mar 8, 2012 at 4:07 | comment | added | arunmur | @ZJR most of them are not my decisions. Its works more like a group decision. I mostly write them, while I do come up with solutions. | |
| Mar 8, 2012 at 4:00 | comment | added | ZJR | Now, what I really don't understand is why you trowed the CouchDB bomb over to an already pretty alienated crowd. You're kind of losing them. Are you at least officially meant to manage the whole project or you just hijacked the scene? | |
| Mar 8, 2012 at 3:48 | answer | added | DXM | timeline score: 6 | |
| Mar 8, 2012 at 3:46 | comment | added | ZJR | Methodologies are so hard with no syntax sugar to easen the pain. (sorry for the half-comment, had slipped on the save button) | |
| Mar 8, 2012 at 3:35 | answer | added | PhD | timeline score: 1 | |
| Mar 8, 2012 at 3:15 | comment | added | dreza | Stick to your guns. Listen to their points of view and if not convinced then be ready to argue your point as to why what you have done will lead to less work and better maintainability in the long run. Lots of head banging and internal swearing will be needed by you. Good luck. | |
| Mar 8, 2012 at 3:03 | history | asked | arunmur | CC BY-SA 3.0 |