This weekly roundup highlights what we believe to be the most thoughtful and/or interesting discussion of the week. We're also be highlighting one particularly cool comment in each installment. ๐
The DEV Community is particularly special because of the kind and thoughtful discussions happening between community members. As such, we want to encourage folks to participate in discussions and reward those who are initiating or taking part in conversations across the community. After all, a community is made possible by the people interacting inside it.
NOTE: I realize we didn't choose winners for last week. I was out on vacation and this completely slipped my mind. While there were plenty of excellent discussions, I'm going to skip over last week โ please forgive me. ๐
Discussion of the Week
For this week, props go to @thekillerrex27 for dropping the prompt: "What was your Dev Journey?"
The comments on this post are a great reminder that everyone starts somewhere and folks who we think of as dev rockstars are in fact just normal people with their own humble beginnings. It's inspiring to hear that there are countless ways to become a dev and that no matter what background you come from, you can be a dev too if you want it and work at it!
Everybody has their own story to tell about how they got into development or why they're getting started. Your story (no matter how grand or insignificant it may feel to you) might be all it takes to inspire someone else out there to get started or keep going. I urge you all to share your experiences and continue building each other up!
Comment of the Week
We'd like to highlight @facundocorradini's thoughtful response to @gabrielpedroza's excellent prompt "Why is CSS Hated On?"
Cause it's out of their expertise. And even alien to their main way of thinking.
CSS has a logic behind it, but it's declarative nature makes it closer to linguistics than to the logical mindset of imperative programming or the spatial thinking of design.
People hating on CSS are either programmers or designers that are trying to shoehorn it into their way of thinking instead of taking the language for what it is: a language.
CSS describes the interface, provides suggestions for the browsers that at the end of the day have the final word on how things are rendered.
That is very different from drawing in a known-dimensions, fixed canvas as designers normally do, and even quite different from the set of logical instructions we write in traditional programming
And honestly, this comment alone doesn't do it justice; you should read the full exchange between Facundo and Gabriel! Reading through this discussion is so helpful for better understanding CSS and why folks often have gripes with it. Rather than try to sum things up myself, I'll just say read the comment(s)! โ๏ธ
What are your picks?
There's loads of great discussions and comments floating about in this community. These are just a few we chose to highlight. ๐
I urge you all to share your favorite comment and/or discussion of the past week below in the comments. And if you're up for it, give the author an @mention โ it'll probably make 'em feel good. ๐
Top comments (4)
๐คฏ Thank you so much and I love that it's helping you work with your wife. ๐
Oh absolutely agree! Abbey's series has been such an enjoyable read. ๐
@facundocorradini not only did an excellent job explaining the fallacy that I've had with CSS but went into multiple in-depth real-life examples (english language and a css example) to make sure I understand what really sets CSS apart from literally everything known to this planet ๐. Thank you for giving exposure to this topic and thank you Facundo for an awesome chat!