The problem with this is that "long" and "short" are subjective. There's no helpful way to determine whether your code is either, save for the feedback of others.https://twitter.com/paulg/status/1126142088976969732 …
If you've worked a lot on a certain class of problems, after a while you find you have intuitions about how much code you'd need to do a particular thing.
-
-
I agree with that. The problem I've had in the past is that one engineer thinks some code is long while another thinks it's short. It usually boils down to differing levels of confidence, not necessarily the code length.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
If nothing else, if you have an alternative solution that you think will be shorter, the definitions of "short" and "long" are irrelevant. "Short" is a direction.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Setting some standard principles for the code base such as “a function should do one and only one thing”, can reduce/shorten the code while improving readability.
@unclebobmartin has some super informative stuff on this matter.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.