Do you use interface as tagging system for the code? [closed]

Question

Do you use interface as a tagging system for the code, or you have a better way to remember which object does what?

how do you keep in mind a complex system, after the use of the abstraction.

Answer 1

• an intuitive package structure
• carefully chosen names
• a comment describing the object's role at the beginning of the class
• a small document describing the "big picture"

Every mind has its limits, we cannot keep in mind large amount of complexities. I would even say that our job, as programmers, is to maintain complexity under control, and there is no silver bullet for this.

The cleaner, intuitive, simpler the system is structured, the easier it is to find one's way through. This is achieved by simplifying things where it can be, by decoupling things, by choosing the right abstractions, the right tools, etc.

Answer 2

I only use interfaces as tags where it is idiomatic in the language/existing source. That practice is uncommon.

As for keeping a complex system in mind after abstraction... Well that's the point of abstraction isn't it? If the system is well designed/abstracted, you don't need to keep the entire thing in mind; just the part you're working on. Good names help, because then you can read cthe code rather than remember what that bad name really means. Good types help, since they have obvious purposes.

Consistency is vital. Then you don't need to remember details about the code since all of the code follows the same style and practices. It is easier to read, and you don't have to read a lot of code to work on the one part of the system because it is easy to infer what the rest of the code does (and how it does it) when the code is consistent.