“No pain, no gain”, so the mantra goes.
The Protestant ethic of “he who is not suffering is sinning” appears in a fascinating, text-book display of cargo-cult programming. “If your code is too easy to write, it will probably have hidden bugs” (“hidden bugs” being the modern equivalent to the unexplained natural disasters of old times, something so scary yet unavoidable that we mortals invent supernatural explanations and rituals to assuage our fears).
Naturally, this leads to the even more ludicrous “with pain, comes gain” — if you want to purify your code from the evil “hidden bugs”, you must undertake painstaking, careful, rites of purification. Like any ritual, its purpose is not merely internal — it must be seen to inspire.
This is the modern excuse for “type safety”, with ugly duplication like “Map<Foo,List<Bar>> var = new HashMap<Foo,List<Bar>>();”, and “wrap all your strings in objects — strings must never be parts of your API” (subtext — if it’s too easy to write, it must be sinful).