3 ms·
I've programmed in some capacity for a long time. I never got into MS programming, except when I was a kid with DOS and some BASICs (gwbasic, mostly). The rea
by hereforphone 5y ago
I've programmed in some capacity for a long time. I never got into MS programming, except when I was a kid with DOS and some BASICs (gwbasic, mostly).
The reason I've stayed away from MS is that it's always felt inelegant to me. Not only are the systems clunky but the code just looks so ugly to me.
AnExtremelyLongFunctionNameThatWrapsTwiceOnTheScreen(MsI.BillGates.IncrementValueOnlyIfNotInWindows95).
It is not an elegant system by any stretch of the imagination. Same goes for Powershell.
- WesleyJohnson 5y agoLong function names are often self-documenting in terms of what they're supposed to do, even if not the how. What's more clear? find_windows_kit_root_with_key find_kit
- shiryel 5y agoThe ideal solution is to use modules/classes and parameters names to contextualize, eg: Windows.find_kit_root(key) And is even better if your language supports pattern match on the parameters like elixir, so you can "overload" the function with many types of arguments, eg: Windows.find_kit_root(%User{key: key}) Windows.find_kit_root(%Admin{key: key}) Providing different behaviors to the same function name