Re:Please do not attempt to simplify this code
by chillacy on Thursday December 27, 2018 @10:53PM
(#18774779)
In the most ideal way, the complexity becomes the code structure. People can only keep track of 7 or so odd things in working memory at a time, we tackle complexity through chunking (abstraction), so that these new 7 things are in turn each 7 more things which are in turn 7 more things (ideally).
[ Parent
| on HN ]
Re:Please do not attempt to simplify this code
by AstralStorm on Friday December 28, 2018 @04:45AM
(#18775845)
Your code structure is not my memory chunking structure and it will interfere.
At a point you run the risk of just overloading memory with way to many names and entities by merciless chunking, not to mention create a file or function maze.
Inlining works surprisingly well because you do not have to memorize things and can just read them. Theoretically it is a tooling problem, but nobody wrote a good enough "inline" tool so instead everyone relies on incomplete and buggy textual descriptions.
Re:Please do not attempt to simplify this code
by chillacy on Friday December 28, 2018 @09:30AM
(#18776873)
I'm not sure what to say, just do the right thing and be more practical than dogmatic I guess? There are situations where it's better not to install an abstraction. There are situations where an abstraction fits super well and is well understood by your dev team.