That sound you're hearing is my head, ringing like a bell that's been given a bloody great whack with a fifteen pound sledge. We just covered "design by interface," which, from the comments, is quite familiar to at least some of you but was a concept I literally could not get my head around reading about it in books. I think I tried to teach myself Java and C# at least five times in ten years, and foundered every time on this concept. It would finally seem that, with the help of a harbor master, I have managed to steer clear of those rocks.
I now know what a nineteenth century shipwright must've felt the first time he ever saw a steamship under way.
Design by interface just seems like a step backwards to me. Completely decoupling code from interfaces is the sort of thing that can only really be done with interpreted languages like C#. .NET is really just space-age Kernel Basic, when all is said and done.
being able to separate the interface is very useful for implementing a service based architecture.
No kidding. I'm just now getting my head around the implications of polymorphism, but it most definitely seems to promise simple solutions to what I once thought were complicated problems which I faced every day. General purpose languages rock!
Posted by: scott on March 23, 2007 05:49 PM