Slightly controversial hypothesis: This expertise is magnified by concise languages. If it takes hundreds of lines of IDE-generated macroexpansions to do anything, you can't see as easily when code is too long.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It goes the other way, too! An experienced programmer will also be extremely suspicious of code that seems like it needs to be longer, given the requirements (e.g. needs to cover more edge cases), but is too short. Will suspect code of being written only for "the happy path."
- End of conversation
New conversation -
-
-
Or code that yields carrect results but seems too short. It either contains an element of genius or it doesn't work for all inputs.
-
I bet it wouldn't take much code to create an edit button.
- Show replies
New conversation -
-
-
An expert knows to make it much longer than it could be, because the priority should be on a future programmer (including you) understanding it.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Some times, we do leave some earlier code as unused functions to be deleted later. (Kind of like we stuff our house with things we don't need anymore but scared to throw away). So may be, running code coverage to make this call is better...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Too complicated to be correct
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This Tweet is unavailable.
-
I'd say CPU speeds appeared to solve that problem until "big data" became en vogue. In those problems, thinking in nanoseconds instead of milliseconds can save you $$$$ on hardware and/or cloud time.
End of conversation
-
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.