Reading well-factored code feels like reading a concise, clearly articulated essay. It's a joy. Meanwhile, reading convoluted, laborious code feels like reading an incoherent rant.
-
Does it mean that we, coders, should spend more time learning how to express our thoughts more clearly - not only in code, but (perhaps even primarily) in writing and speech? Maybe this isn't new, but to me this thought is novel
Programming is thinking clearly, then describing simply.
-
-
But that's not the case most of the time, for many people/companies/projects. We think *somehow*, and we code *somehow*. Clear thinking is not necessary to simply 'make it work' and solve task at hand. That was my point. But now I think I can see the difference. Thank you!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
How one can train itself to think clearer?
-
Or how do we define clear thinking in the first place (given we're talking about solving problems with code)
End of conversation
New conversation -
-
-
... constrained by the language you program in.
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.