On February 11, 2016 we held a seminar and discussions on the topic of “Code Smell”. We tried to identify what are the caveats of smelling code. We have viewed a series of basic examples to identify what is the right way of having the code written and interpreted afterwards. We have also ran a coding round with everybody and changed smelling code into a well-designed piece.
We have alo discussed some good design patterns and best practices that should be applied during all development stages to ensure no code is left to simply work with the assumption that it will be fixed/improved later because it will not.
Basically we’re trying to avoid small issues that can lead to bigger issues later during the development or maintenance of the software product. It also helps in future developments since it leaves a well-readable code for the future.