3 ms·

Of course there's no blog post about how you should use a new piece of tech at your company because you saw a toy example of using it and like it - because when

by sbov 10y ago

Of course there's no blog post about how you should use a new piece of tech at your company because you saw a toy example of using it and like it - because when you put it that way it sounds ridiculous. Instead you have people posting toy examples of code that isn't used in production or is used in production for very specific reasons that usually don't apply, and other people thinking "hey that looks neat" and deciding to use it in production without doing actual analysis. See: the sharp rise of NoSQL and chase of "big (not actually big) data" starting ~7 years ago. If this wasn't a phenomena then the posts you linked seem kinda pointless.

jasode 10y ago
>, and other people thinking "hey that looks neat" and deciding to use it in production That may actually happen but it's not relevant to my point. I'm pointing out that exabrial presented his opinion about choosing "uncool" tech as if he was a lone voice crying out in the wilderness. He's not a lone voice. Even though exabrial ran into a project apparently enamored by shiny new toys, that doesn't take away from the fact that the overwhelming popular opinion is to just use the older stuff. For example, every time a thread about "Javascript fatigue" comes up, the HN commenters pile on complaining about the speed of change in the ecosystem and the flavor-of-the-week framework. No thread about new tech ever has "I'm going to use this brand new week-old framework in production!" as the top voted comment -- nor is there ever an article recommending such a strategy upvoted to the front page. >If this wasn't a phenomena then the posts you linked seem kinda pointless. They're not pointless but they may have been triggered by a sample size of one (Dan M. writing about regrets at Etsy) or zero projects (Jason Kester writing about what he hypothetically would do). Both those blog posts can be written for audience contemplation ... but ... simultaneously not an indicator about most of us being restless programmers trying to deploy shiny toys into production. Based on those 2 blog posts (and many others like them), and the followup comments in HN threads overwhelmingly expressing the same conservatism, I'd say exabrial doesn't realize the majority actually agree with him.

by sbov 10y ago

jasode 10y ago

>, and other people thinking "hey that looks neat" and deciding to use it in production That may actually happen but it's not relevant to my point. I'm pointing out that exabrial presented his opinion about choosing "uncool" tech as if he was a lone voice crying out in the wilderness. He's not a lone voice. Even though exabrial ran into a project apparently enamored by shiny new toys, that doesn't take away from the fact that the overwhelming popular opinion is to just use the older stuff. For example, every time a thread about "Javascript fatigue" comes up, the HN commenters pile on complaining about the speed of change in the ecosystem and the flavor-of-the-week framework. No thread about new tech ever has "I'm going to use this brand new week-old framework in production!" as the top voted comment -- nor is there ever an article recommending such a strategy upvoted to the front page. >If this wasn't a phenomena then the posts you linked seem kinda pointless. They're not pointless but they may have been triggered by a sample size of one (Dan M. writing about regrets at Etsy) or zero projects (Jason Kester writing about what he hypothetically would do). Both those blog posts can be written for audience contemplation ... but ... simultaneously not an indicator about most of us being restless programmers trying to deploy shiny toys into production. Based on those 2 blog posts (and many others like them), and the followup comments in HN threads overwhelmingly expressing the same conservatism, I'd say exabrial doesn't realize the majority actually agree with him.