Skip to content

Replace code smell with code weeds #10

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

professor
Copy link
Collaborator

In the docs folder, we discuss why we prefer code weeds over code smells. This makes that change front and center in the presentation

@benchristel
Copy link
Owner

Sorry I just saw this—I apparently wasn't subscribed to notifications on this repo!

If we're going all-in on the rename, then I think there are some other places that would need to change. E.g. the docs/smells directory. I wonder if there's net value in introducing a new metaphor if we still have to explain the old one (which I agree we should, since "code smells" is the commonly used term).

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

Successfully merging this pull request may close these issues.

2 participants