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.
Discussion of the Week
This week the winner goes to @hr21don who wrote up an interesting prompt under the tag #explainlikeimfive called "Explain JSX like I'm five."
Two immediate things that I enjoyed about this post were 1) it takes advantage of a lesser-used but really quite fun, educational tag (#explainlikeimfive) and 2) it doesn't waste any time or words getting to the prompt. While in most cases, I wouldn't condone leaving the body content of a post empty, here I think it works well; we get all we need in the title!
But obviously, the real draw here is the awesome explanations in the comments! You got explanations that lean on solid examples, those that offer short'n'sweet descriptions, and some folks advising to stay away. As with lotsa tech tools, there are quite a few strong opinions expressed here about JSX. Love it or hate it, join into the discussion and share your thoughts (of course, always respectfully, no matter how strong your opinions may be)!
Comment of the Week
As for our commenter of the week, this one goes to @phlash for their great explanation to @jaminologist's excellent prompt What's The Name of This Password Management Technique and is it a Good Idea?
Effectively you are making your master password a little longer? It also protects slightly against a technology failure of the password manager (Lastpass anyone?), while potentially making it difficult to use autofill.
Perhaps there is a variant solution - where part of the master password is used to unlock the database, and part is held in memory (transiently, never stored) to be appended or blended (XOR'ed?) with the stored passwords before they are used or displayed? Might be an interesting PR for the KeePass(XC) teams!
also - good XKCD reference 😄
@phlash has a history of helpful, thoughtful comments and this one is no different! And, also shoutout-worthy, @jaminologist has been writing some awesome posts since joining our community earlier this month (I recommend checking out the thought-provoking & thorough Diversity & Inclusion In Tech. Who Bears Responsibility? for a sample of Benjamin's work).
The conversation between Phil and Benjamin is exactly the kinda thing we hope for here. Two devs analyzing and discussing a technical topic together on friendly terms — hopefully both of 'em walking away a bit more knowledgeable than they were prior. Really appreciate you two being in the DEV community!
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)
On noes - fame 😁
Thanks dev.to folks!
You're very welcome — thank you! And haha, now I got Bowie's Fame playing in my head... not a bad tune to have on the mind. 👨🎤
Heya! Thank you for the mention and for highlighting my other article! Looking forward to getting more involved with the community in future!
Hey hey! No problem. That really was an awesome article.
So glad to hear that ya plan on continuing to participate in this community! 🙌