> Tons of developers became seniors in < 3 years Complete lunacy. A major reason we have to deal with a never-ending stream of hype vomit is because people im

> Tons of developers became seniors in < 3 years Complete lunacy. A major reason we have to deal with a never-ending stream of hype vomit is because people implement stuff and leave before they have to suffer the consequences of their decisions. It's easy to argue for $thing if you're not the one having to deal with it 5 years down the line. I don't care how smart you are or what you were doing when you were 12; if you haven't dealt with consequences from your decisions (and some consequences from other people's decisions) a few times in a real-world business context with real customers then you're not a "senior". Your "CV-driven-development" CV may be dripping with the right keywords, but that doesn't make you a "senior" either. Their "5 reasons why hiring a great junior is the right bet for you" is even more lunacy to the point of being ageist wank. In what kind of universe is "reuse the same technologies from previous companies" bad in and of itself? Using stuff you know works well, so you know where the problems are, instead of betting on some unproven tech that may or may not work well and that may or may not cost the company millions. Just because "it's a bit nicer" or whatever. The largest group should be the new blood" just translates to "most people should be unfamiliar with the code base and have no idea what they're doing". Worst article I've seen posted to HN in a long time, by a considerable margin.