2 ms·
I gave a lot of thought on that example when I first watched the video many many years ago. And I think it all comes down to experience and it has far less to d
by axegon_ 6y ago
I gave a lot of thought on that example when I first watched the video many many years ago. And I think it all comes down to experience and it has far less to do with good taste. To a junior developer the first solution is perfectly valid and easy to read for everyone. And it is true to a certain degree. But it takes some experience and sooner or later you start getting this feeling that doing something like this probably has a simpler and easier solution, for after all, this is a common thing. Once people wrap their head around that concept(the "surely I'm not the only one that's faced that" thought), they start finding it very easy to jump between languages and learn new ones with ease.
- setr 6y agoAnother aspect is that as a codebase develops, memes inevitably appear; patterns and strategies that replicate themselves throughout the codebase. The elegant utility may be difficult to deal with standing alone, but when you see it 2,3,4 different places (by same author, or mimics) it becomes normalized, and once normal there’s really no reason not to use it. The main problem with clever code is when it stands alone. Which is also the context in which these debates occur.