DEV Community

Discussion on: Frontend Development 2021

hyggedev profile image
Chris Hansen • Edited on

I think you are spending too much time critiquing.
Also, learning sass is important as many organizations use it. It produces cleaner CSS, and helps with cross browser compatibility. Not to mention, learning CSS was listed second on his list of subjects to learn, and Sass as forth.
Also, one of the best features in some CSS in JS is nesting, along with other Sass like features. Essentially, if you only understand CSS, you'll only be hindering your capabilities and understanding of CSS in JS. For example, styled-components is a lot more powerful if you have preexisting knowledge of Scss.

Lastly, everyone needs a GitHub. I see people trying to make a point where you don't need one. Some say recruiters don't care or have no ability to read code anyhow. But the thing is, majority people in the field will tell you, the further you go through the interview process, you'll eventually land in front of the lead developer or engineer, who's going to decide on whether your skills are up to par, and can contribute to the team. One should hope they have a GitHub that day. I have also heard numerous times, where during the interview, the developer has been asked to walk through code on their GitHub. Rather than a white board.
I would also add, that GitHub is the Instagram of git management, whereas gitlab is myspace.

I hope I don't sound harsh! 🤣 I just don't see the need to "proof read" or "correct" what's been said here. All solid points IMHO.

lukeshiru profile image
Luke Shiru • Edited on

I'm not saying "sass is not important", it can be useful (like less), the thing is it isn't "essential". You don't HAVE TO learn it in order to be a front-end developer, and having alternatives like CSS Modules or CSS-in-JS, if you'll mention SASS, you have to mention those as well. There are other items like "basic understanding of HTML, CSS and JS" which I agree with.

If an interviewer takes GitHub as a metric to hire a dev, and they don't hire you based on that, then you basically dodged a bullet. There are folks with hundreds of GitHub repos that aren't as good devs as folks with 10 or less, so using that to make a decision is not ideal.

You don't sound harsh at all (I mean the "you are spending too much critiquing" is kinda acid, but not that much). I just gave my feedback. I enjoy being active in DEV, and that includes doing comments like this one.

Thread Thread
hyggedev profile image
Chris Hansen

Hey, right on, solid points. I can appreciate you sharing your thoughts and not beating around the bush 👍
I guess it's just one of those situations where it all "depends", right? Some may like Sass, some may rather have you be a superstar at CSS. And to touch base on the Github matter, you could totally be right. I hear mixed opinions. Having a public repo may even expose you in some horrible way. But I have also heard people getting jobs with just HTML and CSS alone, which is crazy, but it seems to be true! ✌️

Thread Thread
dannyengelman profile image
Danny Engelman

Ah, the endless debate on learning the Technology or the Tool.
CSS is the Technology, Sass is a Tool.
And a Fool with a Tool is still a Fool.

natescode profile image

False. Everyone that doesn’t have skills or experience needs GitHub, ie bootcampers.

I’ve interviewed at and worked for Fortune 100 companies. My Github is absolute crap and I have only been asked for it two times over which of those times I never gave it.

So for all my bootcamper students who can barely code, yes a good GitHub is extremely important. BUT once they actually have a résumé and actually have real skills it’s about as valuable as a cover letter