The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
If you drink tea with milk, and your wife drinks her coffee black, then the black coffee may cool down more quickly (all other things being equal, black "stuff" heats up/cools down faster than lighter-coloured "stuff").
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
we have a lot of class where all properties are readonly and have constructor with 40+ parameters to initialize those said properties.
And, in the unit test code with have code like
publicstatic T EmptyConstructor<T>()
This is the kind of typical web developer code that make me sick to just look at it.
Where do web developers learn to code?
That seems to be fairly typical practice for web developer to do that, but it makes me want to vomit!
constructor with lots (I mean, 40+ mandatory parameters) is kind of a bad idea (i.e. an endless source of pain)
having all property setter, and the using reflection to call the private setter anyway, or having zillion of mandatory parameters and using reflection tricks to automatically fill them for you is what I would call bad practice and generally cause endless source of perfectly avoidable pain, while providing little concrete benefit (more like, what if benefits)
not too mention such code has bad performance and is hard to understand and modify, quite often.