re: What are you not interested in learning? VIEW POST

FULL DISCUSSION
 

The modern frontend toolchain is where I'm tapping out on the "full-stack" idea. I can do everything I need to do with server-rendered templating languages; if I'm working on something that requires getting serious about understanding React or Vue or Webpack, I'm going to be working with someone who knows React or Vue or Webpack. I can work out what's going on in there well enough to fix problems and add minor features, but I'm profoundly disinterested in digging deeper.

 

I've done the whole frontend toolchain thing. Webpack manually, webpack with code generators, vue, this tool, that tool. I hope I'll stay away for a while :D

I seriously like Babel though. It started as a way to use modern javascript in lacking browsers but it's becoming more and more a way to experiment with features before they are standardized

 

Same here. It feels like a waste of time learning anything as before a year has passed almost everything is irrelevant again. It is just to too much effort to keep track of everything that's going on there, besides keep track of everything in the back end.
I used to consider myself a full stack developer. But with the modern front end stack I think everyone who claims they are full stack are liers.

 

I suggest digging deeper, you never know when a job comes along that if you can do that you'll get it because you can do it and others can't. Not all systems are new systems, the backbone of most of the internet is running on stuff from before most of us were born.

Being able to maintain and rework legacy systems is pretty lucrative and generally a requirement as your career progresses, trust me.

code of conduct - report abuse