3 ms·
What about developers experience? Would a 2 year experienced developer ever call a 30 years experienced developers code 'readable', 'maintainble', (add more buz
by mironathetin 12y ago
What about developers experience? Would a 2 year experienced developer ever call a 30 years experienced developers code 'readable', 'maintainble', (add more buzzwords)? Probably not. The older developer may use constructs that the younger has never heard of. If the consequence is, use simple code that everybody can understand, then we never use all of our potential.
My hunch is, it is crucial to keep developers and avoid situations where you have to maintain other peoples code as much as possible.
Just a quick idea, as I was writing this:
Lets compare software with fiction: assume, an author has written a quick draft for a story. It works great, it has more potential, some parts still don't fit in.
Would you honestly take the story away from the author and give it to a handful of others to finish it and turn it into a bestseller? It is likely, that you get a mix of styles that gets worse and worse, the more people touch it.
Sounds familiar?
- mhomde 12y agoAn author can give a book to different people for proofreading, copyediting, and substantive line Editing. Some of the "voice" of the author might indeed be lost just because good copy editing normally is about 20% of a draft , but it could be argued that what's left is better for it. I agree though that one should try to keep the overall tone/style the same
- mironathetin 12y agoThis procedure is called code review in software development. If done right, it can add great value to code especially, if the author has the last word and we coders develop the gentleness of the best fiction editors.