This article is the third part of "Eliminating Code Smells Through the Use of Simple Refactorings". In the first two parts, we wrote about refactoring through simple changes and execution path changes. You can access these articles on our blog–Part 1 and Part 2. In the present article, we give a few tips and examples on refactoring through design changes. Design changes usually ...

The article is a continuation of "Eliminating Code Smells Through the Use of Simple Refactorings" where we wrote about refactoring through simple changes. You can access the article here: http://www.blog.tecknoworks.com/posts/code-smells-1/  In this part, we give a few tips and examples on refactoring through execution path changes. Execution path changes. These are more comple ...

Synopsis  I’m going to start off by explaining the concept of refactoring, what is it useful at and when it should be applied. Then I’m going to dive into the three big types of refactorings that I’ve come across in my experience: the simple changes, the execution path changes and the design changes. In order to determine the need for refactoring we must be able identify certai ...

2 days. 12 hours of intense coding. More than 40k data points and 700 lines of code. Tons of coffee. We can predict the future. Tecknoworks wins first place. This pretty much sums up our experience at the 2016 CEE Microsoft Azure Machine Learning Hackathon. For me personally, it has been an incredible learning experience that I would recommend on top of each coder’s bucket list ...

Throughout the development phase of a software product, there comes a time when the source code needs maintaining. Think of it like a nice living fence that needs trimming every other week, to make sure it has just the right shape and aesthetics. That's right—code can, and should be aesthetic, easy to read and comprehend. The process through which one achieves this is refactori ...