Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Favorites |
infavorites:mine infavorites:1234 |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Questions about interface related design considerations, such as programming to the interface.
3
votes
6answers
OK. I am learning design patterns. Every time I see someone code an example of a design pattern they use interfaces. Here is an example:
http://visualstudiomagazine.com/Articles/2013/06/18/the … -facade-pattern-in-net.aspx?Page=1
Can someone explain to me why was the interfaces needed in this example to demonstrate the facade pattern? The program work if you pass in the classes to the facade instead of the interface. If I don't have interfaces does that mean
…
asked Nov 7 '13 by Kyle Johnson
2
votes
I think it is overkill. If the user of your API does not need to be forced to implement/use something a certain way then I would leave it out. Interfaces are contracts, if I don't need it then why … give me one?
I think people overuse interfaces. You are adding a layer of complexity that is not needed in most cases.
…
answered Dec 6 '13 by Kyle Johnson
