There are many reasons for the problem you describe. Some that I can think of are: There are a lot of self-taught programmers. Even the good ones are only aw

There are many reasons for the problem you describe. Some that I can think of are: There are a lot of self-taught programmers. Even the good ones are only aware of a small portion of the accumulated 40+ years of knowledge in CS and SE - theory and practice. So they re-invent techniques, methods, etc thinking they have discovered something new. Since much of the literature is secreted behind paywalls, you can't really blame them. I have noticed some academics have a fondness for "putting old wine in new bottles" and applying fancy new labels. Then when you do a keyword search their "new" method, technique, framework, etc they look like inventive geniuses. Many young academics also suffer from problem as described above. You simply get no respect if you confess to using a framework, technique, methodology that was in widespread use 10+ years ago. It's always way cooler to be using whatever the popular flavour of the day might be.