I read this article on HN today from 1986 http://worrydream.com/refs/Brooks-NoSilverBullet.pdf , and just like The Mythical Man Month(btw, when was the last time you saw some overpaid manager refer to this? Exactly) it seems as relevant as ever. Yet there is little or no talks, interview questions or tutorials from the big companies on this. But Google have a lot of fancy HTML5 web worker articles and other esoteric chrome tech that won't be relevant or production ready for several years online In the end anything can be built on anything to some extent, if you use ES6, Go or Rust is a very small part in the whole. It's always overestimation, "why can't we reuse X" and overselling that fails software projects. For every year I work, I feel more and more everything is just the same. Small vs thin client cycles, big vs small UIs, SQL vs something else, "this is the year of functional programming" in an infinite loop of stupidity Is there a lack of historical knowledge or are older engineers just jaded and don't care anymore to bring this up?
It’s like training machine learning algorithms trying to find the global maxima: it is often trapped in local maximas, or performing even worse than the previous runs. I guess it is similar for any kind of exploration, including tech.
My amateur opinion is that for example lawyers have a much better understanding of history and use cases, and often refer to old ones and why the succeeded/failed
Just stumbled upon this 4 years late but the answer is actually quite simple — audience size. Engineers aren’t empowered to have a say or implement the things you’re talking about until they’re Senior or sometimes Staff depending on the topic/company. We often have to disagree and commit. So you’re targeting a pretty small audience relative to the juniors/mid levels who just wanna learn new tech and solve a project in a neat way
Sure, at a certain level you know when to scalve vs good enough etc. But my other point is a bit, why is there so many stupid "how to do X in React hooks" by some high level Facebook guy when the audience can learn it anyway and not more "How we handle the more programmer less producitivyt on FB" posts which is the important thing