Hierarchy of utility classes behind a facade?
Question
What practices exist when it comes to organizing utility classes where some could be subset of others?
As an example, you could have a FileUtil class with methods related to Files and a subset of this class for checking File formats.
No correct solution
Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow