Whenever I see "Tutorial: X" on the internet I immediately think "What if a beginner read this".
Therefore whenever I see an article without a "Do not do this in real-life / production because..." warning I immediately take a negative view.
In this case I evaluated the site with that in mind, all the techniques are useful but the examples are pretty badly shoe-horned. There are much cleared ways to give examples of multiple assignments than the examples there.
Other things like writing methods on one line, probably useful in situations like defining error classes
"class MySpecialError < StandardError; end" but apart from that I frown upon it.
There is also the "Hey, this is a nested ternary operator" example which is... well, demo'ing nested ternary operators without a big fat "Do this in real life and people will hurt you" warning is a no-no in my book.
A bit rambling but I suppose to sum up my main problem with this was "Here are some things you can do" without actual discussion about when they are suitable, when they are not, and why this is so.
Therefore whenever I see an article without a "Do not do this in real-life / production because..." warning I immediately take a negative view.
In this case I evaluated the site with that in mind, all the techniques are useful but the examples are pretty badly shoe-horned. There are much cleared ways to give examples of multiple assignments than the examples there.
Other things like writing methods on one line, probably useful in situations like defining error classes
"class MySpecialError < StandardError; end" but apart from that I frown upon it.
There is also the "Hey, this is a nested ternary operator" example which is... well, demo'ing nested ternary operators without a big fat "Do this in real life and people will hurt you" warning is a no-no in my book.
A bit rambling but I suppose to sum up my main problem with this was "Here are some things you can do" without actual discussion about when they are suitable, when they are not, and why this is so.