"... the arrogance and self-indulgence of youth." s/youth/younger programmers/ How can they make work for themselves? 1. Do what's already been done, not eve

"... the arrogance and self-indulgence of youth." s/youth/younger programmers/ How can they make work for themselves? 1. Do what's already been done, not even knowing it's already been done. 2. Declare "rot" or some similar claim of obsolescence and proceed to redo what's already been done. There's nothing necessarily awful about this unless they fail to do a better job than the earlier effort. Alas, this is too often the case. For a variety of reasons. In the early days, portability was a higher priority. Not to mention longevity. Because everything was expensive. Today's software "rots" a lot faster than the software from the early days of computing, IMO. And so the younger programmers have lots of "work" to do. Yet I do not see much progress being made. Because I do not measure progress by productivity alone. Programmers who can churn out code in a dozen different languages to do the same old things are a dime a dozen. As a user, I do not want software that needs to be updated every week. Poorly written software and gratuitous use of network bandwidth. But I can see how programmers who love writing code would enjoy this state of affairs.