Closed nylanderdev closed 3 years ago
What is the purpose of this? What do we gain from removing the prefixes?
It's important to establish proper conventions early on in development. The "I" prefix is somewhat frowned upon, and for good reason (see quote).
"I prefer to leave interfaces unadorned. The preceding I, so common in today’s legacy wads, is a distraction at best and too much information at worst. I don’t want my users knowing that I’m handing them an interface." - Robert "Uncle Bob" Martin, Clean Code
It's important to establish proper conventions early on in development. The "I" prefix is somewhat frowned upon, and for good reason (see quote).
"I prefer to leave interfaces unadorned. The preceding I, so common in today’s legacy wads, is a distraction at best and too much information at worst. I don’t want my users knowing that I’m handing them an interface." - Robert "Uncle Bob" Martin, Clean Code
The reason why I added the prefix was because a lot of new people had interest in the project, and I wanted to make it more obvious what each type was.
Thanks for the quote. But this doesn't sound like a full explanation. Why would you want to hide the fact that you're handing the users an interface? How can this information become too much, why is it harmful? I'm very interested in learning more about this.
Codecov Report
Continue to review full report at Codecov.