Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSTips Labels / Tags #287

Closed
pastrop opened this issue Feb 25, 2016 · 7 comments
Closed

JSTips Labels / Tags #287

pastrop opened this issue Feb 25, 2016 · 7 comments

Comments

@pastrop
Copy link

pastrop commented Feb 25, 2016

Overall thought about the selection criterion for JSTips: I think a priority should be given to the tips useful for practical development problems that JS developers are facing that are not well addressed in the existing resources. Just to give a few examples: Lately, I have been coding using MEAN stack. There are a very few resources addressing issues associated with NPM Mongoose (MongoDB module for NodeJS) integration (i.e save() method is sporadically stops working, upsert option in findOneAndUpdate() has a new flag that has to be included if you want this method to work for new entries in to be added to the DB although this information is nowhere to be found in documentation.) Another good example is from my recent experience with the front-end dev't: if you need to find out in JS which cell in the table is clicked on, you should be really attentive how you do it because this click events tend to fire multiple times on every click. Again, good luck with searching for a solution for this. It'll take you a while....Those are just examples. I think this sort of tips are much more valuable than, say, discussions on the way of using prototypical inheritance patterns. Doug Crockford is a pretty good source for those. So, except you can prove you are better better than Doug, read the book first and submit your tip later if you still think it is valuable....There is no point of covering issues that are well covered in the literature and/or are all over Stackoverflow. Just my 2 cents.....

@calderaro
Copy link

L

El jue, feb 25, 2016 06:24 PM, pastrop [email protected] escribió:

Overall thought about the selection criterion for JSTips: I think a
priority should be given to the tips useful for practical development
problems that JS developers are facing that are not well addressed in the
existing resources. Just to give a few examples: Lately, I have been coding
using MEAN stack. There are a very few resources addressing issues
associated with NPM Mongoose (MongoDB module for NodeJS) integration (i.e
save() method is sporadically stops working, upsert option in
findOneAndUpdate() has a new flag that has to be included if you want this
method to work for new entries in to be added to the DB although this
information is nowhere to be found in documentation.) Another good example
is from my recent experience with the front-end dev't: if you need to find
out in JS which cell in the table is clicked on, you should be really
attentive how you do it because this click events tend to fire multiple
times on every click. Again, good luck with searching for a so lution for
this. It'll take you a while....Those are just examples. I think this sort
of tips are much more valuable than, say, discussions on the way of using
prototypical inheritance patterns. Doug Crockford is a pretty good source
for those. So, except you can prove you are better better than Doug, read
the book first and submit your tip later if you still think it is
valuable....There is no point of covering issues that are well covered in
the literature and/or are all over Stackoverflow. Just my 2 cents.....


Reply to this email directly or view it on GitHub
https://github.com/loverajoel/jstips/issues/287.ñ

@zenopopovici
Copy link
Collaborator

@pastrop Everybody is more than welcome to contribute with a PR. We're not refusing anything that is of interest.

@kurtextrem
Copy link
Contributor

kurtextrem commented Feb 26, 2016 via email

@ro0NL
Copy link

ro0NL commented Mar 3, 2016

Perhaps each tip should be indicated with some sort of level? i.e. beginner, medior, pro?

@zenopopovici
Copy link
Collaborator

@ro0NL Not a bad suggestion ... //cc @loverajoel

@loverajoel
Copy link
Owner

@ro0NL @zenopopovici yep, we can create labels or tags and I jekyll support this

@zenopopovici zenopopovici changed the title JSTips Value-add JSTips Labels / Tags May 6, 2016
@zenopopovici
Copy link
Collaborator

Merged with: #368

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants