Timeline for Interfaces and abstraction: takes more time?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 18, 2016 at 11:55 | history | edited | gnat | http://meta.programmers.stackexchange.com/questions/7285/structured-tag-cleanup-initiative-phase-ii | |
| Apr 26, 2014 at 18:06 | history | tweeted | twitter.com/#!/StackProgrammer/status/460117824078618624 | ||
| Apr 26, 2014 at 16:30 | comment | added | Brandon | A good litmus test I find with creating interfaces is if my interfaces should only have a single implementation, then they are a poor interface. Look out for things like IWidget and WidgetImpl. That suggests a split with no purpose other than to say you split it into an interface. | |
| Apr 26, 2014 at 14:48 | answer | added | Euphoric | timeline score: 5 | |
| Apr 26, 2014 at 14:13 | answer | added | Thiago Silva | timeline score: 3 | |
| Apr 26, 2014 at 12:05 | comment | added | Sebazzz | No, the applications a certainly meant to last long. And the requirements do change, yes. I just often find resistance against such changes in architecture or even TDD (arguments like 'I have not seen in working', 'Manual testing will always be required' or 'If the requirements change I need to change both test and production code'. | |
| Apr 26, 2014 at 12:00 | comment | added | MetaFight | Also, for what it's worth, it sounds like you're applying your SOLID principles correctly... though it's hard to tell without knowing more about the questionnaires and the business domain. It's possible that your coding is fine, but your domain model is flawed. We can't tell. | |
| Apr 26, 2014 at 11:57 | comment | added | MetaFight | It's really a matter of what's the company's bottom line. Are you there to churn out short-lived applications as quickly as possible? Or are you there to build a system which will need to live for years, gradually adapting to changing requirements? If your case is the former, then you could probably get by without SOLID principles. I've been in that situation, and it's no fun for the dev, but it's not wrong per se. If your case is the latter, then SOLID will save you money and your sanity over the years. | |
| Apr 26, 2014 at 11:25 | history | asked | Sebazzz | CC BY-SA 3.0 |