Group items tagged

"This blog poses a rather radical premise. It suggests that Refactorings have counterparts called Transformations. Refactorings are simple operations that change the structure of code without changing it's behavior. Transformations are simple operations that change the behavior of code. Transformations can be used as the sole means for passing the currently failing test in the red/green/refactor cycle. Transformations have a priority, or a preferred ordering, which if maintained, by the ordering of the tests, will prevent impasses, or long outages in the red/green/refactor cycle."

"The greatest advantage that JetBrains ReSharper provides is that it makes the improving process much cheaper. How it is done? By simplifying both of the improvement steps: Understanding the code - ReSharper provides very quick and simple navigation along with immediate usage information. Changing the code - ReSharper provides extensive refactoring options. Most of the known refactoring techniques are built-in."

At which point do you refactor code to make it clean?

"In my post on Why SOLID Matters, we refactored a small piece of code to be more SOLID.  Granted, it was a simplistic example, but good for illustrating several key points on SOLID.  We will continue using the same code to discuss the benefits of Mocking."

"But even in today's SW industry, there does not seem to be much of an expectation from SW professionals that we should have the 'capability/tools to build our own tools' that do much of the project work for us. I am not talking about the simple automation, things like rename/refactor or autocorrect, or intellisense and all that, I am talking about the kind of automation and tooling that writes or deploys software for us and saves hours, days and weeks of our time from handcrafting software solutions from scratch again."

I've found that there are three basic types of duplication that we can eliminate from our code that successfully build on each other.