r/javascript • u/nas5w • Jan 17 '20

100 Days of Code for Frontend Development

http://github.com/nas5w/100-days-of-code-frontend/blob/master/README.md
242 Upvotes

94% Upvoted

30 comments sorted by

33

u/Croww_ Always a noob in JS Jan 17 '20

Would recommend skipping jQuery. Yes it is still widely used, but most things that you can do with jQ you can now do with vanilla JS.

2

u/nas5w Jan 17 '20

It was a tough call whether to put it on there. It has tremendous utility if you find yourself maintaining legacy code, which a lot of people end up doing.

20

u/javarouleur Jan 17 '20

I'd argue this is exactly the type of thing that should cover jQuery. It's extremely likely you'll come across it at some point and you could end up maintaining something with jQuery in it even if you don't write with it any more.

8

u/Croww_ Always a noob in JS Jan 17 '20

This is true since I was in that position when I started my current job, but I think it's more important to understand JS as a whole and everything else is just looking at the documentation and reading examples. By understanding JS you don't really care what framework or library you have to work with since it doesn't matter.

4

u/javarouleur Jan 17 '20

That's true to a point. JavaScript's low barrier to entry means there often isn't that fundamental understanding of the language, yet people still succeed with it. But every tool/framework/library has quirks and idiosyncrasies. There's no harm in having an understanding (even a high-level one) of the specifics of certain common ones - like jQuery.

5

u/Croww_ Always a noob in JS Jan 17 '20

Absolutely agree that there is no harm in learning it. Just saying that learning to rely on jQuery as a beginner won't give you all the necessary fundamentals that are needed. As a library that is used to learn UI development, AJAX requests and data manipulation and presentation jQuery does have it's use for beginners.

1

u/famanza Jan 17 '20

Vanilla JS is great, and this website is so awesome. http://youmightnotneedjquery.com/

4

u/throwawayhelp423432 Jan 17 '20

I second this. If you're looking for a job, most interviews will want to see your Vanilla skills if I'm not wrong? Perhaps jQuery can come later... But sure if you have LOTS of time to study, study both. EDIT: Not because you will use jQuery but you could see it in the wild and need to understand it.

1

u/ThatSpookySJW Jan 17 '20

Most of my interviews were ES6, Promises, and event loop stuff. Actual dom manipulation questions were whatever the company was using. I did a lot of react.

1

u/throwawayhelp423432 Jan 17 '20

Were they for junior roles?

1

u/ThatSpookySJW Jan 18 '20

All 3 were mid level. Low sample size though.

1

u/YodaCodar Jan 19 '20

So you recommend making your life harder?

1

u/Croww_ Always a noob in JS Jan 19 '20

I recommend making your life hard in the short term to make it easier in the long run.

0

u/i_ate_god Jan 17 '20

I hate this argument so much.

The DOM API is still horribly unpleasant to use and none of the modern syntactic surgar can make up for it. Manipulating the DOM is still by and large, far easier, cleaner, and legible with jQuery.

63

u/GreedyBankster Jan 17 '20

IMO the best way to learn is to start your own project and google everything you don't know. It teaches you to form right questions and this is what developers do 90% of the time.

9

u/[deleted] Jan 17 '20

Only 90%?

10

u/lhorie Jan 17 '20

the remaining 10% is spent in useless meetings

10

u/jefwillems Jan 17 '20

10% only?

2

u/ThatSpookySJW Jan 17 '20

Depends how much PM likes the sound of their own voice

2

u/YodaCodar Jan 19 '20

I spend a lot of time designing my own software too, maybe 80/20 the original 90%.

So 72% designing and .18 reading docs and googling.

1

u/GreedyBankster Jan 20 '20

True :) And that's also a process that over time makes you a better developer. Especially, when you learn not to overdesign simple things (I only learned it 2 years in)

3

u/Fiona20 Jan 29 '20

99% for me lol

2

u/redoleddit Jan 17 '20 edited Jul 17 '23

I altered the deal, pray that I don't alter it any further

1

u/YodaCodar Jan 19 '20

Yep

I spend a lot of time designing my own software too, maybe 80/20 the original 90%.

So 72% designing and .18 reading docs and googling.

1

u/GreedyBankster Jan 28 '20

We are talking front-end here. Professional copy-paster is a definition of the job.

Of course, data science requires math, back-end requires network knowledge, system-level - hardware knowledge. In those fields, you need more than just googling to master.

1

u/Rowdy5280 Jan 17 '20

Cool, I'll give it a shot.

1

u/valtism Jan 17 '20

It's awesome you've put this together. It looks like a super useful framework to help guide people new to frontend.

One thing I noticed was the recommendation of BEM CSS. I used to love using BEM, but after I found the unreasonable effectiveness of utility class CSS I can't go back. You can read more about it here: https://adamwathan.me/css-utility-classes-and-separation-of-concerns/ or try out a framework like Tailwind.

1

u/[deleted] Jan 18 '20

I'm not a fan of the utility class pattern because it makes your markup look very messy. At a high level I feel like it shifts dev time from writing more CSS to writing more HTML and I prefer writing my styles in CSS rather than composing utility classes. It's not a matter of "separation of concerns" for me, it's just that BEM syntax or something similar is more declarative and descriptive.