3 ms·
It would be one thing if we just knew these companies used these technologies, and that was it. Instead, we have conference talks, testimonials, and evidence th
by staticassertion 10y ago
It would be one thing if we just knew these companies used these technologies, and that was it. Instead, we have conference talks, testimonials, and evidence that they are working well for them.
Obviously you should not use a technology without understanding it. Does this really require a discussion? No one is on the other side. But going "Well that technology is just hype" isn't understanding it, it's dismissing it.
- cle 10y agoConference talks, testimonials, etc are often biased towards the positive. It drives me nuts when someone tells me why I should use some technology, without telling me why I shouldn't use it, and what its constraints and limitations are. Those are equally as important as the features. Project documentation are the worst at this, painting a rosy picture of how the tech will solve the world's problems, without telling you the practical realities of using it.
- staticassertion 10y agoRight, because there isn't a litany for what could go wrong with every single technology mentioned in this article already... Let's not pretend like there's a single technology out there that isn't constantly under fire. If you strip out the strawman argument against each technology ("Let me tell you a story about how this technology didn't work in my imagination") you end up with one single premise - do research before adopting tech. Did you need to be told that? I think if one single person is making tech stack decisions in production and no one is going "uh can you justify this" you have far more serious issues.
- cle 10y agoNo I don't need to be told that. That's my point. Most tech products make it difficult for me to do my up-front research, because they want to paint a rosy picture of their product to drive adoption. But I'm less likely to adopt it if I can't easily understand its constraints, failure scenarios, scaling bottlenecks, maintenance headaches, leaky abstractions, etc.
- staticassertion 10y agoCan you name a tech product that is hard to research in regards to its constraints or failings?
- deleted 10y ago[deleted]
- electric_sheep 10y agoThe React and Redux devs engage in more self-critique, and are more honest and open in the shortcomings of their approaches, than just about anyone I know of in web development. From the author of Redux: https://medium.com/@dan_abramov/you-might-not-need-redux-be46360cf367 https://medium.com/@dan_abramov/you-might-not-need-redux-be4... From the official React docs: https://facebook.github.io/react/contributing/design-principles.html https://facebook.github.io/react/contributing/design-princip...
- staticassertion 10y agoNo, no! It's all just hype! Don't look at new technology!
- cle 10y agoGlad to see! Thanks for sharing. I hope this trend continues.