Unraveling Software Antipatterns and Smells Definitions
Resumo
Software technical debt may persist if the root cause is misidentified. We argue that this stems from misconceptions about antipatterns and smells. This article reviews the literature to clarify their similarities and differences. Findings suggest that both terms are used interchangeably, with “smell” being more common, though this ambiguity may affect optimal solutions in software projects.
Referências
Fowler, M., Beck, K., Brant, J., and Opdyke, W. (2018). Refactoring: improving the design of existing code. Addison-Wesley.
Sabir, F., Palma, F., Rasool, G., Guéhéneuc, Y.-G., and Moha, N. (2019). A systematic literature review on the detection of smells and their evolution in object-oriented and service-oriented systems. Software: Practice and Experience, 49(1):3–39.
Tahir, A., Yamashita, A., Licorish, S., Dietrich, J., and Counsell, S. (2018). Can you tell me if it smells? a study on how developers discuss code smells and anti-patterns in stack overflow. In Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018, EASE ’18, page 68–78. ACM.
