Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Front End Development Topics to Learn in 2019

zendev.com

Post reply on HN
Print view View original

71–80 of 143 posts

Re: Front End Development Topics to Learn in 2019

#71

Post by uhoh-itsmaciek »

karmakaze wrote: post #55
ui-explorer12 wrote: post #37

Earlier quoted context omitted.

Why would someone need to preemptively learn both React and Vue? I can get saying you want to understand how they accomplish their respective roles, but is there an actual (non-crazy) scenario where your core, day-to-day job depends on really knowing both? Or is that the whole point? Am I erroneously assuming "learn" means really deep knowledge(which for me really digging into any single one of these would be enough)…

I'm primarily a back-end dev but do some front end work which is mostly React. I didn't like it much and thought there should be something better. Learned Vue on my own time, which was only a few hours. Did a super simple side project to work around some common gotchas. So glad I did, now use Vue for all new work and encourage people at work on greenfield projects. Now, I'm playing around with alternate state managem…

What did you dislike about React? What does Vue do better?

Re: Front End Development Topics to Learn in 2019

#72

Post by vmware505 »

gwillz wrote: post #23
burnt_toast wrote: post #10

Earlier quoted context omitted.

It's frustrating how the go to solution for a problem tends to be to install another module. I agree it's not smart to keep reinventing the wheel, but when the solution takes less than 15 minutes to implement the recommended answer shouldn't be another module.

This is exactly my gripe with it all. There's always 10 different solutions to the same problem, often in 10 different packages. Typically, I've seen it come about because often package creators have no interest in maintaining their invention. Their PR list is huge, all the tickets are just questions about "why isn't my PR merged?". So someone else creates an alternate or a fork, but so does everyone else. I don't th…

Hence I prefer opinionated, convention over configuration solutions. It exists in Javascript world also. It called Ember.js. ;)

Re: Front End Development Topics to Learn in 2019

#73

Post by james_s_tayler »

jenscow wrote: post #19
Jeaye wrote: post #16

Has anyone realized the wheels on the treadmill are spinning toward the carrot? Shouldn't be tough to keep up.

ah.. perhaps the aim is for the developer to escape the carrot.

edit: you have much to learn young grasshopper

Re: Front End Development Topics to Learn in 2019

#74

Post by ollerac »

pascalxus wrote: post #64

It's pretty difficult to keep up with all the new frameworks these days. That's why I created a faster way of learning. I noticed that everytime I wanted to learn a new framework or new library, I was always creating examples and modifying them to learn how they worked. So, I created a Tutorial/Example code website that combines tutorials with real working examples: https://codeorc.com By not having to set up every s…

I've taught people coding a few times and I always start with a game, but it's hard keeping it simple enough for them to understand. This tutorial looks like a great place to start. Thanks!

Re: Front End Development Topics to Learn in 2019

#75

Post by olingern »

juddlyon wrote: post #4

This is a solid list, but front end dev has gotten a bit absurd. I feel like I need to install 86,000 dependencies via NPM to do something that server-side frameworks already figured out. I was following a simple Vue/Vuex tutorial the other day and my node_modules directory was 200MB+. Use yarn or npm to install XYZ.... What's the difference? Why do I have to google this as step 0? Why do you assume I know the intric…

I can't really understand the sentiment that front-end dev is absurd. I started with .NET years ago and find _anything_ that becomes 'standard' in the front-end more approachable than the constant reinventing of the wheel / new framework releases MS did circa 2004 - 2014.

It was something like:

- Learn ASP, opps we meant ASP.NET web forms. Actually, we meant .NET MVC.

- Oh no, the world wants APIs ... please learn WCF. Actually, we meant .NET Web API.

It seems things have finally calmed down with .NET core. But, along with the MS frameworks you also need to have good command over C# and data access / manipulation utilities such as LINQ, Entity Framework, etc. If you happen to be working with MSSQL Server as I was -- you had to learn it and all of its quirks.

I will say the tooling, once learned, was pretty good everywhere (except WCF in terms of configuration). I can't say that for a lot of front-end utilities, which I think results in a lot of configuration pain and StackOverflow searches.

I do find the answers / guidance on configuring front-end much higher quality than most things in the MS ecosystem, though.

____

My intent here isn't to bash MS so much as it is to point out that the breadth of things you actually have to learn for front-end development is less than some other ecosystems. We're a part of a privileged profession where income and demand is high, so I do expect re-skilling to be an ongoing process.

Re: Front End Development Topics to Learn in 2019

#76

Post by austincheney »

Many comments here are concerned with the ever changing trends, downloads, and such. Frontend technologies really don’t change that fast.

If being a stronger frontend developer is a priority focus on the basics. I have received some favorable feedback about this list that requires no additional downloads https://github.com/prettydiff/wisdom/blob/master/Web_Educati...

Re: Front End Development Topics to Learn in 2019

#78

Post by calibas »

olingern wrote: post #75
juddlyon wrote: post #4

This is a solid list, but front end dev has gotten a bit absurd. I feel like I need to install 86,000 dependencies via NPM to do something that server-side frameworks already figured out. I was following a simple Vue/Vuex tutorial the other day and my node_modules directory was 200MB+. Use yarn or npm to install XYZ.... What's the difference? Why do I have to google this as step 0? Why do you assume I know the intric…

I can't really understand the sentiment that front-end dev is absurd. I started with .NET years ago and find _anything_ that becomes 'standard' in the front-end more approachable than the constant reinventing of the wheel / new framework releases MS did circa 2004 - 2014. It was something like: - Learn ASP, opps we meant ASP.NET web forms. Actually, we meant .NET MVC. - Oh no, the world wants APIs ... please learn WC…

A while ago you could get away with doing front-end dev with nothing but a text editor and an FTP client, compared to those days I can see how things seem absurd now.

Re: Front End Development Topics to Learn in 2019

#79

Post by digitalzombie »

vertline3 wrote: post #62

Uhm I... I just think it's a bit like quicksand. In a few years, things will have shifted somewhere else. A percentage of our time should be on staying current, anyone have a good strategy?

> anyone have a good strategy?

I left the industry for data science. Went back to school and fall in love with statistic. Going to try to get a biostat job. I'm trying to do side projects web app and not give a damn about the flavor flav of the month.

I don't know if that's a good strategy.. it's basically peacing out. I also move most of my tech stack to plain old stuff like a simple mvc framework and no frontend rendering.

Re: Front End Development Topics to Learn in 2019

#80

Post by smokeyj »

kokokokoko wrote: post #32
juddlyon wrote: post #4

This is a solid list, but front end dev has gotten a bit absurd. I feel like I need to install 86,000 dependencies via NPM to do something that server-side frameworks already figured out. I was following a simple Vue/Vuex tutorial the other day and my node_modules directory was 200MB+. Use yarn or npm to install XYZ.... What's the difference? Why do I have to google this as step 0? Why do you assume I know the intric…

I understand your frustration. One thing I'd like to mention is that a comment similar to your comment is frequently mentioned in any HN post about typical frontend/JavaScript topics. So frequently, that I'm not sure what it adds to the discussion at this point. It's possible you are not aware of that and just wanted to let you know.

Honestly I think it's just a meme at this point. Don't fight it. Just mention something about Electron being bloated and rake in that sweet sweet karma.

Hey, has anyone else noticed how bloated Electron is? I bet it's all those rootin tootin NPM packages!

Post reply on HN