Timeline for Decoupling classes from the user interface
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2014 at 18:26 | comment | added | Frank Hileman | While I appreciate efforts to improve software design, substituting a call on an interface, for a call on a class, does not decouple anything semantically. Consider what happens when using a dynamically typed language. There is far too much emphasis on superficial (syntactic) decoupling, and little on true decoupling, in the advice provided in the programmers section of stack exchange. | |
| Jul 29, 2011 at 21:45 | comment | added | Boris Yankov | You first need to know how to engineer something in order to over-engineer it. In my experience, people 'under-engineer' software much more often. | |
| Jul 29, 2011 at 21:26 | comment | added | snakehiss | -1 In my experience one of the most common problems is premature generalization and over-engineering in general. | |
| Jul 27, 2011 at 15:04 | comment | added | Boris Yankov | MVVM is silimar to MVC. MVC is mostly for stateless applications like web apps. | |
| Jul 26, 2011 at 20:13 | comment | added | Patrick Hughes | +1 You can even use MVC for not-web applications, at the very least it helps you think in terms that keep the responsibilities clear. | |
| Jul 19, 2011 at 4:24 | history | answered | Boris Yankov | CC BY-SA 3.0 |