You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reason: It's incredibly heavy on terminology never encountered before which causes frustration when trying to understand. Spending 20 mins trying to understand 10 new terms/concepts in just one paragraph out of a very lengthy article isn't very effective learning imo. You're put in a position to try and parse everything sentence by sentence or accept you can't understand half the things they're talking about. I like to understand what they're talking about so then I can understand examples and conceptualize them in my mind. I can't do that in this article since every paragraph needs to be deciphered thoroughly.
E.g. "The strategy used by redux-saga is to use objects that represent future computations. The idea is similar to returning a monad, except that it doesn’t always have to be a monad that gets returned. Monads are capable of composing functions with the chain operation, but you can manually chain functions using imperative-style code, instead."
I also checked discord questions about this article to confirm I wasn't the only one struggling with it. There were other people suggesting it was hard to read/shouldn't be in the "More Tests" section.
Checks
Describe your suggestion
Article in question: https://medium.com/javascript-scene/mocking-is-a-code-smell-944a70c90a6a
Reason: It's incredibly heavy on terminology never encountered before which causes frustration when trying to understand. Spending 20 mins trying to understand 10 new terms/concepts in just one paragraph out of a very lengthy article isn't very effective learning imo. You're put in a position to try and parse everything sentence by sentence or accept you can't understand half the things they're talking about. I like to understand what they're talking about so then I can understand examples and conceptualize them in my mind. I can't do that in this article since every paragraph needs to be deciphered thoroughly.
E.g. "The strategy used by redux-saga is to use objects that represent future computations. The idea is similar to returning a monad, except that it doesn’t always have to be a monad that gets returned. Monads are capable of composing functions with the chain operation, but you can manually chain functions using imperative-style code, instead."
I also checked discord questions about this article to confirm I wasn't the only one struggling with it. There were other people suggesting it was hard to read/shouldn't be in the "More Tests" section.
Path
Node / JS
Lesson Url
https://www.theodinproject.com/lessons/node-path-javascript-more-testing
(Optional) Discord Name
No response
(Optional) Additional Comments
No response
The text was updated successfully, but these errors were encountered: