|
|
|
|
|
|
by michaelcampbell
3333 days ago
|
|
|
> > Preferring implicit code is optimization for the first person writing the code while making it harder to understand, debug, and update. > I feel that this argument has been repeated so often that it's almost understood axiomatically: nobody thinks about what it means anymore, it just "seems true". Indeed. It seems just another way to not understand "everything is hard to read until one learns to read it". |
|
|
So everything is equally difficult to read and understand? There are articles that say "great software is like Shakespeare" and others that say "great software is like Hemmingway". Which one of those authors is easier to read and understand, as someone who speaks English natively?
As someone who has inherited just two code bases, I know first-hand that there can be massive differences in how easy something is to read and understand. One of my companies had a code base that non-technical people could read and even send PRs for. Another of the code bases took months of ramp-up time.