loading...
Cover image for Top 5 DEV Comments from the Past Week
The DEV Team

Top 5 DEV Comments from the Past Week

peter profile image Peter Kim Frank ・1 min read

This is a weekly roundup of awesome DEV comments that you may have missed. You are welcome and encouraged to boost posts and comments yourself using the #bestofdev tag.

Replying to If I don't use React, am I still a developer?, @jdmg94 talks about the essential ingredient to that abstract question of "what makes a developer":

I think what really makes or breaks a person as a developer is the ability to move data around.
It doesn't matter what language or framework you use, once you know how you want your data to flow through your application you can implement it however you like. Knowing how to handle data structures, how to communicate through the application, that is what makes you a developer, knowledge of the language is important but once you can handle data flow, then you can pick up a language/framework and get productive. but that is just my opinion of course.

The What am I doing here? article inspired a number of great comments about belonging and imposter syndrome.
At the top of the thread was @madnesslabs 's take:

Been doing this for 10 years and it doesn't matter how long that imposter syndrome never truly goes away. Plus, being at meetups and socializing is another anxiety causing thing.

The best thing you can do is remember that we are all learning, the games are made up, and the points don't matter! 😉

And as a community we try to remember stories like this so we remain warm and welcoming to others. This stuff is hard, no matter who you are, and it's impossible without asking for and receiving help. Good luck on your journey and we're always here is you need help along the way!

The Best productivity tools for your dev life is an incredible resource — @anacondaqq added even more value to the conversation by talking about their favorite productivity tool:

I tried all the tools above. And stay not satisfied.
Then I found some time ago quire.io/ and stick to it. Love it, and enjoy it.

Quire.io is:

  • Right now free
  • Like workflowly / moo.do
  • Have Kanban and Boards too
  • Nested tasks
  • Instant notifications
  • Comments for projects, tasks, whatever
  • Apps for iOS / Android / Chrome Extension
  • Detailed documentation with explaining all features: quire.io/features
  • You can migrate from any other tool to QUire
  • Black (night) theme (really beautiful)
  • tags, timers, GitHub integration, etc, etc.
  • The service can work without internet (very useful when you have no wifi but wish to continue to work with your tasks)

Start reading from here: quire.io/w/Getting_Started_with_Qu...

Try it, you will found it very powerful (personally I think that the tool is the most powerful right now in the whole market).

I'm not involved anyhow to this company, I'm not related to this company, I'm just really happy client which finally found what I did search for.

Following up on What's a Design System and why you need one, @emmawedekind adds valuable context and clarification around Design Systems and and what they're comprised of:

Hi Tomek! Nice post! We should be careful when using the term Design System to only describe the physical design assets and branding guidelines! A Design System is made up of the Design Language (design assets like Sketch Kit, AI Kit, etc. and branding guidelines such as accessibility, motion, etc.), Component Library (coded components usually in React, Vue, Angular, or another popular JS library/framework), and the style guide (which are the physical websites you've linked above that document the design language & component library).

We often see designers use the phrase "Design System" to describe the Design Language and developers use the phrase "Design System" to describe the Component Library & Style Guide, but it's really all of these things.

You can take a look at my slides if you would like to learn more :) slides.com/emmawedekind/design-for...

Finally, @12vanblart jumps into Why do you use jQuery in 2019? to drop their take on jQuery's longevity:

I have no evidence to back this up, but I'd be willing to guess that it's not about what jQuery does that vanilla can't do easily, so much as one of the following:

  • Supporting a legacy codebase
  • Not knowing that vanillaJS has feature {x}
  • Familiarity with JQuery - For example: If you had to choose between looking up how to do something in vanilla or already knowing how to do it in JQuery, which would you choose?

See you next week for more great comments ✌

Discussion

pic
Editor guide
Collapse
peter profile image
Peter Kim Frank Author

Congrats to @jdmg94 , @madnesslabs , @anacondaqq , @emmawedekind , @12vanblart for making the list this week!

Collapse
madnesslabs profile image
Madness Labs

Thanks for the mention, we meant every word! 😄

Collapse
emmabostian profile image
Collapse
terabytetiger profile image
Tyler V. (he/him)

Brb, putting "Making educated guesses" on my resume!

Collapse
jdmg94 profile image
José Muñoz

awesome :)