To me code smell is a clue that some code might be badly written. But it's not proof - and there could be good justification for the smell. An example would be

To me code smell is a clue that some code might be badly written. But it's not proof - and there could be good justification for the smell. An example would be a 500 line method. Antipattern is more serious IMO because of the work "pattern", i.e. "something repeated". It is a repeated occurrence of doing something badly (in someones opinion!) across the code base. An example that comes to mind is making references to packages that you don't want structurally in your dependency graph, just to use a utility function.