2 ms·
> This is meant literally. Reading existing code is difficult -more difficult than writing code- thus it is a genuine take from the developer that throwing ever
by ChrisMarshallNY 6y ago
> This is meant literally. Reading existing code is difficult -more difficult than writing code- thus it is a genuine take from the developer that throwing everything away and starting over from scratch is “easier” than continuing on the existing. [Ergo this is flawed for non-small projects because the new development will never catch up with the existing during the tenure of the developer(s).]
I tend to work alone, so the poor schlub that needs to go in and maintain the code is usually Yours Truly.
That’s a big reason that I am pretty obsessed with heavily-documented code. I eat my own dog food.
It is quite painful to review undocumented codebases; even (especially) really well-written code. I write in Swift, and it’s entirely possible for an experienced Swift programmer to write highly efficient code that is almost completely inscrutable.
Not sure I’d necessarily call that “technical debt,” but it’s a real issue.
I’ve learned to use naive coding (in reality, highly efficient code often doesn’t buy squat), and a lot of “this is why I did this” commenting, along with long, descriptive entity names[0]; assuming that it’s my goal for my code to be maintained by others, and to not have them constantly pinging me with questions.
I will say that the (fairly ambitious) projects I’ve done that have grown into large community efforts, have resulted in very, very few questions about the code. It seems that understanding the code I write, isn’t an issue, for most people.
I write code for myself, and that seems to make others happy.
[0] https://medium.com/chrismarshallny/leaving-a-legacy-1c2ddb0c8014 https://medium.com/chrismarshallny/leaving-a-legacy-1c2ddb0c...