Java interfaces explained
5th December 2002
While browsing through Kasia’s Java Archives I came across this gem explaining why interfaces are such a useful feature of Java:
One thing they do quite well is hide the implementation from the calling classes. Why is that good? Well, when you want to change the implementation you don’t have to change the calling classes.. Saves time, saves work, saves QA resources, code is more readable, more versatile and easier to maintain.
I’d seen this explained before but the example Kasia provides finally made it click for me. Kasia also provides a link to Design Techniques, a collection of articles on good Java design. I just wish I’d found these before I started on our (now handed in) Java coursework.
More recent articles
- Qwen3.6-35B-A3B on my laptop drew me a better pelican than Claude Opus 4.7 - 16th April 2026
- Meta's new model is Muse Spark, and meta.ai chat has some interesting tools - 8th April 2026
- Anthropic's Project Glasswing - restricting Claude Mythos to security researchers - sounds necessary to me - 7th April 2026