C#C
C#15mo ago
workani

✅ Do I always need to avoid coupling?

For example, I have a class Application where the main part of my project's logic is written, and I also have a GenerateVocabulary object which will itself use an Interface to actually generate content. Will it be good practice to simply create this object inside my Application class? And in general, is it acceptable in a professional context to create one object inside another if I'm 100% sure that I won't change it?
Was this page helpful?