!(x, y, z)
Underrated measure of code complexity: the number of things you have names for. This is why I like higher order functions. You don't need as many parameter names.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Our solution to that at @naologicerp is to write code in 3D perspectives. Source code changes depending on a designated "observer". In data relation-intensive apps (like ERP) that transforms complexity into a linear function (as opposed to quadratic)
-
I am very interested to know more about this topic and about your reply. Any articles to know more details about your meaning for applying that in erp? Thanks
- Show replies
New conversation -
-
-
K/Q/J encourage this a great deal, the drawback is that you tend to end up with write-only code.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Excel won because it doesn't make you name your variables first. Inverted UX is so pervasive in computing: forced to choose a date on calendar before you know they're free, email subject before body, file name before contents, function names/types before body. Deserves essay.
-
Compare: ⌘-C, ⌘-V with SCP args. Intentful vs. inverted UX is a form of biculturalism that touches on Left vs. Right: how many walls/types/ordered tar arguments should we have between our programs? The dynamic left wants data; the static right, types. Inbetween, we have pipes.
End of conversation
New conversation -
-
-
Depends on how local these names are. Having a lot of things to name that only matter in small local context is OK. Having a lot of terms that you have to know to understand the whole codebase is not
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This is why I like anonymous functions.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This is one of the most underrated advantages of a functional style over others: usually, names only need to be defined when needed. Avoids having to give uninformative names, but, unless used judiciously, you may end up writing long, incomprehensible chained expressions.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
yes exactly! I hate when people split out sequential code into multiple small functions, the argument passing everywhere drives me insane. Each argument needs a name. Of course there are good reasons to split functions, but some people just go too overboard with it
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.