36 ms·
On a related note, I've seen people taking this too far in functional/procedural code. Not every concept needs its explicit name, not every function needs to be
by TeMPOraL 6y ago
On a related note, I've seen people taking this too far in functional/procedural code. Not every concept needs its explicit name, not every function needs to be 5 lines of code or less. All that jumping around between function definitions is a serious impediment to readability.
(EDIT: this is mentioned in the article as "localization complexity")
- sitkack 6y ago> Not every concept needs its explicit name There is a special subgenre of functional programming, where the style is to explicitly not have names https://en.wikipedia.org/wiki/Tacit_programming https://en.wikipedia.org/wiki/Tacit_programming (also known as point-free)
- dsego 6y agoI've been thinking about it lately. Esp. since I've taken another look at the refactoring chapters of Clean Code, but instead of being enlightened I felt disgusted. Like, for-loops are ok, if-statements are ok, those are the basic constructs of code, you can see the shapes visually and it's easy to follow the code path. This is what you find in low level C/C++ code, lots of switches, loops and conditionals. Those programmers just get used to the verbosity and look at shapes instead of reading line by line. Maybe it's easier for subtle mistakes to pass unnoticed, but refactoring out everything into layers of abstraction brings jumping around and context switching between these different pieces and trying to make a mental picture of how it all fits together.