Such a great job of framing the issue. I love apply, I wish people knew it so I could use it. But is add.apply(null, [10, 20]) more readable or understandable than const [x, y] = [10, 20]; add(x, y) or some other variant? Maybe, maybe not. It depend on who you're working with! And if I'm being honest, it probably isn't more readable in any situation. And only once in a blue moon do I use it.
Then the functional vs OO, and promise chain vs async await is so great. I caught myself thinking, "but async await is more imperative. Even if it is the new shiny!" And there lies the problem.
This is a great article. I'm going to keep it in my back pocket the next time we do an interview.
Aside: putting together a good interview seems to be an art in itself, I'd love to hear some new ideas in that space
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Such a great job of framing the issue. I love apply, I wish people knew it so I could use it. But is
add.apply(null, [10, 20])more readable or understandable thanconst [x, y] = [10, 20]; add(x, y)or some other variant? Maybe, maybe not. It depend on who you're working with! And if I'm being honest, it probably isn't more readable in any situation. And only once in a blue moon do I use it.Then the functional vs OO, and promise chain vs async await is so great. I caught myself thinking, "but async await is more imperative. Even if it is the new shiny!" And there lies the problem.
This is a great article. I'm going to keep it in my back pocket the next time we do an interview.
Aside: putting together a good interview seems to be an art in itself, I'd love to hear some new ideas in that space