“God’s namespace” is a (unusual) term for a template (anti?) Similar to “an object of God” when you type a metric ton of things (mainly methods / functions) that are not or are not closely related to one another huge namespace / static classso that it can be used in several sections of your project.
When you follow this pattern (anti?), You often static class Assetsend up with C # as an example, with a bit of a lot of methods that are mostly unrelated to one another but used in many places in your project (s).
I usually approach this problem, letting the next one Assetsgrow as much as I bear it, and then desperately trying to sort its contents into several smaller ones, based on criteria that seem most legitimate, for example MathAssets, or BitmapAssets, or RNGAssets, and then finally forget about what I put where ... and create a new one Assetsfor several new methods that do not fit into any of the already damped SomethingAssetsprojects.
Are there any other ways to clarify the "namespace of God"? Or do I just need to live with a good old static class Assets?
source
share