Code Smells, a rise to maturity

telanova: the outsourced IT team that feels like your own

Providing advice, consultancy, helpdesk, monitoring and maintenance, updates, upgrades, security: all the things your in-house team would do, but better and at a fraction of the cost and hassle.

Code Smells, a rise to maturity

The smell of Orchids

Today’s world is full of an increasing amount of program code. Back in 1999 Martin Fowler[1] defined the basis of Code Smells. Smells, being the inherent way humans in nature detect bad, and good things, likewise, Code has a smell, be it bad or good. A bad code smell being code that contains bad programming techniques, duplicate code, ie. poor quality. A new paper called Code Smells, by Peter Kokol, Milan Zorman, Bojan Žlahtič, Grega Žlahtič [2] , has been published.

Kokol’s paper[2] analysed the rise of discussion around code smells. Using bibliometrics to analyse research papers which contain references to code smells, Kokol was able to map and detect the changes in frequency and geographical distribution of papers.

Their results highlighted 337 publications which contained references and of those 70% were related to conference proceedings. Which they concluded may mean that code smells is still in the rising state of maturity.

They plotted the details on a timeline and identified that the largest rises were in 2009, then in 2014. They also identified which countries were using the term the most, and as might be expected USA was top, with almost twice the next country, Italy. Italy contained the individual institution that had produced the most papers, with 19 papers published by the Universita degli Studi di Milano.

The research papers indicated that code smell research was split into 3 themes, smell detection, software refactoring, development & anti-patterns. Of these themes code software development and anti-patterns, was the most popular themes, using anti-patterns and knowledge of software development problems code quality can be increased.

Overall an interesting and highlighting paper that shows that in the future, machine learning, and other analysis tools may be used against software development code to identify if it smells of sulphur or wild orchids.

[1] M. Fowler, Refactoring: Improving the Design of Existing Code., Reading: Addison - Wesley, 1999.

[2] Peter Kokol, Code Smells, 2018

#telanovaReporter

Looking to test the quality of your IT configuration, talk to our consultants about what changes you can make to get that wild orchid smell :

Call telanova on 01344 567990

Email Facebook Google LinkedIn Twitter

We use cookies to provide you with the best possible experience in your interactions on our website

You agree to our use of cookies on your device by continuing to use our website

I understand