I know this feeling well. A big part of my motivation for starting dev.to was a feeling of "screw this, I'm just going to go build a basic Rails blog".
Easier said than done, but I've tried to put myself in a position where I can be on the slightly later end of the adoption cycle where there's just fewer things going on because we tend to settle on a few good ideas in a space (for a short while at least).
Iβm a web developer & data visualizer working at a think tank in D.C. I'm a self-taught dev trying to better my skills. I spend most of my time on the front end of the stack.
Location
Washington, D.C.
Work
Lead Developer at Center for Strategic and International Studies
There is nothing more illustrative of the developer attitude than starting your own blog & along the way thinking about how cool it would be to add other user accounts so people can comment, and then maybe post, and wouldn't it be cool if you could follow each other... π
I created the comment section up on a weekend I had told someone I would write a post on a specific topic for them and was procrastinating biiiiiggggg time π
The year was 2016 when I read somewhere that Angular 1 is dead. That was the very first framework I've ever learned in my life. I started jumping from framework to framework trying to learn the next big thing before I was left behind again. Years later (2019 basically) I land my first job and one of the biggest projects in the company is using the very same angular-1x that I ran away from because of some internet hype.
This is not only just a minor feeling to beginners, but it can also completely derail the learning path of a beginner if they're not careful.
I once heard a quote, actually about video games but it seems to have stuck with me and can be applied to other things as well: "Video games are a big deal because a big deal is made of video games". A bit of a self-fulfilling prophecy. I think the same thing happens in IT.
The hype that gets generated can keep you on this strange hamster wheel where you're never learning anything properly but keep jumping from one thing to another. I've been on that wheel and it's not a good feeling.
I find tools like this: thoughtworks.com/radar and this: cncf.io/projects/ to be very useful to show how mature something is and is good guidance for me whether or not to spend my time investigating into a particular tool.
Programmed Canon Canola calculators in 1977. Assorted platforms and languages ever since. Assisting with HOPL.info.
I am NOT looking for work -- I've got more than enough to do.
Location
Perth, WA Australia
Education
A few diplomas.
Work
Software Engineer at [Daisy Digital](https://daisydigital.com.au/)
The flip side of this though is that the playing field does change. SNOBOL4 is insanely powerful tech but no one bothers with it anymore because it's not "new" (is there a word that means besotted with the new simply because it's new?) COBOL likewise. I'd love to stay with the stuff I started to get good at but there's no work there and no money. So I do C# and JavaScript instead.
Good article. I also struggle in similar ways because I also have a life outside of IT (which currently includes long-ferment wild-yeast breads.)
I generally glance over a tech when I hear about it. To figure out what I can do with it. If I might have a future use case I might try it out. In the end I will only really look into technology when I have an actual need for it.
I think the nodejs/JavaScript community really gave a boost to the highly volatile and short lived framework du jour.
I saw that thanks to someone Tweeting it at me. Guess I am not the only one that thought of this pop culture reference when thinking about this topic. I think I win when it comes to cover art though! π
I agree, many waste far too much time chasing new languages and tech. Give time for new stuff to settle mean while we can use what we know to solve real problems people face!
So the next time someone starts tossing around terms you think you "should" know, remember that person probably doesn't know a thoroughbred from a draft horse.
β€οΈοΈπ
We're a place where coders share, stay up-to-date and grow their careers.
I know this feeling well. A big part of my motivation for starting dev.to was a feeling of "screw this, I'm just going to go build a basic Rails blog".
Easier said than done, but I've tried to put myself in a position where I can be on the slightly later end of the adoption cycle where there's just fewer things going on because we tend to settle on a few good ideas in a space (for a short while at least).
There is nothing more illustrative of the developer attitude than starting your own blog & along the way thinking about how cool it would be to add other user accounts so people can comment, and then maybe post, and wouldn't it be cool if you could follow each other... π
I created the comment section up on a weekend I had told someone I would write a post on a specific topic for them and was procrastinating biiiiiggggg time π
The year was 2016 when I read somewhere that Angular 1 is dead. That was the very first framework I've ever learned in my life. I started jumping from framework to framework trying to learn the next big thing before I was left behind again. Years later (2019 basically) I land my first job and one of the biggest projects in the company is using the very same angular-1x that I ran away from because of some internet hype.
This is not only just a minor feeling to beginners, but it can also completely derail the learning path of a beginner if they're not careful.
Wow! I never thought hype could go as far as being destructive to ones career but clearly it can. Thanks for sharing!
I once heard a quote, actually about video games but it seems to have stuck with me and can be applied to other things as well: "Video games are a big deal because a big deal is made of video games". A bit of a self-fulfilling prophecy. I think the same thing happens in IT.
The hype that gets generated can keep you on this strange hamster wheel where you're never learning anything properly but keep jumping from one thing to another. I've been on that wheel and it's not a good feeling.
I find tools like this: thoughtworks.com/radar and this: cncf.io/projects/ to be very useful to show how mature something is and is good guidance for me whether or not to spend my time investigating into a particular tool.
Oh cool, those sites look great for helping decipher technologies. Thanks for sharing!
Thanks for the links. ThoughtWorks keeps surprising :)
The flip side of this though is that the playing field does change. SNOBOL4 is insanely powerful tech but no one bothers with it anymore because it's not "new" (is there a word that means besotted with the new simply because it's new?) COBOL likewise. I'd love to stay with the stuff I started to get good at but there's no work there and no money. So I do C# and JavaScript instead.
Good article. I also struggle in similar ways because I also have a life outside of IT (which currently includes long-ferment wild-yeast breads.)
YAGNI!
I generally glance over a tech when I hear about it. To figure out what I can do with it. If I might have a future use case I might try it out. In the end I will only really look into technology when I have an actual need for it.
I think the nodejs/JavaScript community really gave a boost to the highly volatile and short lived framework du jour.
There is a good podcast with this same title π syntax.fm/show/035/keeping-up-with...
I saw that thanks to someone Tweeting it at me. Guess I am not the only one that thought of this pop culture reference when thinking about this topic. I think I win when it comes to cover art though! π
Hahaha true!
I agree, many waste far too much time chasing new languages and tech. Give time for new stuff to settle mean while we can use what we know to solve real problems people face!
Related:
Do you ever feel like you're stuck with the wrong technology?
Zohar Peled γ» Sep 24 γ» 1 min read
It's temporary phenomenon. Now the front-end is getting stable and the focus is transiting to AI. So I think we can relax ourselves.
β€οΈοΈπ