Five things I will learn just in time for them to become obsolete.
Front End Development Topics to Learn in 2019
11–20 of 143 posts
Re: Front End Development Topics to Learn in 2019
#12Does anyone have something for backend or even better system wide? What correlates with that "3 mos" concept.
Re: Front End Development Topics to Learn in 2019
#13This article makes it sound like the grid layouts of the CSS Frameworks have a legitimate reason for updating. Is this a matter of swapping out grids?
Re: Front End Development Topics to Learn in 2019
#14This article makes it sound like the grid layouts of the CSS Frameworks have a legitimate reason for updating. Is this a matter of swapping out grids?
Used by them. It is a new property added to CSS language
Edit: well, parent was a question that is now edited
Re: Front End Development Topics to Learn in 2019
#15This 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…
npm hell, I assume it's still a thing?
Oh, yeah, it is. I used to love npm and then didn’t use it for several years. I’ve gone back to it lately and find myself screaming “what have you people done?!” on a regular basis now.
And while we’re on the subject of package managers; do we really need so many? I know npm is terrible but it seems like everyone has decided to create their own now. I swear to god I had to use a package manager to install a package manager the other day.
Re: Front End Development Topics to Learn in 2019
#16Has anyone realized the wheels on the treadmill are spinning toward the carrot? Shouldn't be tough to keep up.
Re: Front End Development Topics to Learn in 2019
#17This 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…
What's a language/domain/framework that's _not_ like this? After spending a few weeks struggling with Bazel and Spring you'll not convince me Java is any better.
Had a colleague try and show me, a non Java guy, modern Java + maven + archetypes... It did a lot of downloading, a lot of building and then built something which, when we ran it, hung. I still have no idea what the demo was supposed to show me.
Going to continue working with Go
Re: Front End Development Topics to Learn in 2019
#18This 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 think it's weird to compare server application development to client development which is an entirely different beast.
Client development on any platform is more complicated than the server stack. Back-end API devs have a much simpler job for most apps too. We as back-end devs like to pretend otherwise even though our app runs on just one machine.
Re: Front End Development Topics to Learn in 2019
#19Has 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.
Re: Front End Development Topics to Learn in 2019
#20This 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…
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.
why?
I mean it takes far less than 15 minutes to install a module, so why should I implement it myself?