Which hyped technology did you refuse to learn?

・1 min read

Working with software engineering and programming is being placed in a dynamic and challenging environment daily. New technologies appear, others disappear and most of them are constantly changing, enhancing their capabilities and improving their performance.

This scenario makes learning and keeping yourself up to date an important aspect of this type of career. Despite that, sometimes we ignore brand new technologies that are booming in popularity and trending in the developer ecosystem.

That may happen due to a variety of reasons: disliking a new language's syntax, finding a learning curve too steep or simply enjoying the toolkit you are most familiar with.

Which technologies were trending at a certain point but you refused to learn and why?

Did you find this post useful? Show some love!
DISCUSSION (13)
 

Still holding out for when I’m eventually right about react 😂. Mostly syntax and the fact that I feel it’s overkill for many frontends it’s used for, but I’m also completely aware that I’m in the wrong on at least the first one.

 

React JSX syntax does for HTML exactly what XSL did for XML. I enjoyed XSL so I love JSX.

 

Ruby on Rails, because I had to make a choice in what I learned based on my available time, so I pursued learning more about php, which I was already using, as well as Javascript.

 

Makes sense. Did you at least get a chance to experiment with RoR a little bit? Do you intend to give it a shot?

 

Also, it did fill a little hype-filled, and DHH of Rails / Basecamp fame, seemed, to be honest, very arrogant. I heard more than one tech person look at a web site and say "that looks like a RoR site", like somehow the design was specific to RoR, so that felt like hype-cruft.

I understand how you feel. I like Ruby because it is fun to write and Rails is a great framework for prototyping, but I see why others wouldn't like it

Right, I'm not at all suggesting the hype was real, I just didn't have time to investigate.

 

I didn't, because I was freelance then (and now), so anything I did to learn was "on my own dime", so I just focused on the tools where I already had plenty of good work.

 

I would say all of those reasons are poor ones for not learning something further - I dislike the syntax of some of the languages I use for instance - but my liking of the syntax has nothing to do with how well that language can solve my problem. Learning curves being too steep can definitely make it difficult to try something out, or really get to know it well in order to judge it properly, but in that case I would say - break it down into simple parts so it can be evaluated in a digestible format over time. Simply enjoying the toolkit you are most familiar with is something I see many developers suffer from, but again, at the end of the day this is not why we chose language/framework/lib a over b (hopefully) - we chose these things because they help us do are jobs faster/better and improve the end product. Also - not that this was the point of your post, but I wanted to say that while we all know using a tool just because of its hype is not great reasoning alone, neither is refusing to learn a tool because of its hype. Right tool for the right job<3

 

Maybe it's not clear in the post that those are examples of possible reasons, not the only existing ones.

Furthermore, when I mean refusing, I obviously don't mean ignoring a technology that is a best fit for a job because you dislike the syntax.

The idea of the post was to discuss which technologies had a peak of in popularity and yet you chose to not deeply explore it, not necessarily in a professional scope, but for personal projects.

 

No, it's clear - still feel the same way about those examples.

I know what you meant by refusing, hence my comment - "Also - not that this was the point of your post".

I have not had this happen to me - because I can't think of a reason why I would not explore a new technology deeply. Regardless of scope.

Sorry if I offended you, not my intent. If you have a suggestion of how I could explore this more deeply, as you say I am not - let me know.

When I said deeply explore it, I meant the technologies not the post.

Your comment was a valuable addition to the discussion. Sorry about my tone, last few days been rough

 

I will begin with an example of my own. Nodejs just couldn't get to me. Writing backend with javascript like syntax didn't appeal to me.

Classic DEV Post from Nov 19 '18

What’s a concept you understand now, but took you forever to grasp?

I’m sure we all have plenty of answers to this one, but sometimes we forget how...

Vinicius Stock
I'm an engineer with a passion for innovation, machine learning and coding! Currently working a lot with Ruby.

DEV Tip: When you see a dev.to post you like, follow the author to get more of their posts in your feed.

Happy Coding ❤️