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

More Testing: That the "Mocking is a Code Smell" article be taken out #28584

Closed
2 of 3 tasks
Dimitrije108 opened this issue Aug 6, 2024 · 1 comment
Closed
2 of 3 tasks

Comments

@Dimitrije108
Copy link

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

@MaoShizhong
Copy link
Contributor

Closing as it's a duplicate of #28355

Do feel free to add your comments to that issue if you feel there's more to add to it

@MaoShizhong MaoShizhong closed this as not planned Won't fix, can't repro, duplicate, stale Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants