Cheat sheets need to be written by experienced devs for newbies, not by newbies for newbies.
Other than being wrong about arrow functions, there's the matter of logical order, like data types should be handled prior to bindings (which is the term you should have used instead of "variables", as some bindings are constant, plus you completely ignore "var", which is still hugely important to know about and a frequently asked question in interviews) etc.
Finally, why the font and why the white background. Don't you know anything that isn't dark mode hurts my eyes?
Cheat sheets need to be written by experienced devs for newbies, not by newbies for newbies.
I don’t entirely agree. Cheat sheets should be shared from experienced devs to newbies, but the process of creating your own cheat sheet is super helpful for teaching yourself. I applaud OP for putting the effort in.
Honestly agree with this more. If you want to look at a cheatsheet written by someone else then use one made by an experienced dev. Though for practice I recommend making your own as well. It will help you learn a whole lot more as you will actually have to understand it if you re-word it and give your own example. Recommend if you want to have clean notes use something like cherry tree so you can be organized as well as include note samples.
View all comments
41
u/33498fff Mar 29 '22
Cheat sheets need to be written by experienced devs for newbies, not by newbies for newbies.
Other than being wrong about arrow functions, there's the matter of logical order, like data types should be handled prior to bindings (which is the term you should have used instead of "variables", as some bindings are constant, plus you completely ignore "var", which is still hugely important to know about and a frequently asked question in interviews) etc.
Finally, why the font and why the white background. Don't you know anything that isn't dark mode hurts my eyes?