Comments on: Code Refactoring Guidelines

By: Karl Kemerait

Karl Kemerait — Sun, 03 Jan 2010 14:43:32 +0000

Another article on the importance of refactoring code… http://designlunacy.blogspot.com/2009/06/basic-design-philosophy.html

By: links for 2009-06-26 at Mior Muhammad Zaki: PHP & JavaScript Programmer

links for 2009-06-26 at Mior Muhammad Zaki: PHP & JavaScript Programmer — Fri, 26 Jun 2009 18:47:37 +0000

[...] saved 30 Useful PHP Classes and Components, 10 great articles for optimizing MySQL queries and Code Refactoring Guidelines on [...]

By: Top Posts 2008

Top Posts 2008 — Sat, 10 Jan 2009 15:26:38 +0000

[...] Code Refactoring Guidelines (6 comments) [...]

By: Velneo es igual a ahorrar tiempo y dinero | Blog de Velneo

Velneo es igual a ahorrar tiempo y dinero | Blog de Velneo — Wed, 19 Nov 2008 11:09:15 +0000

[...] que el desarrollador tenga que hacer nada. Nada, literalmente. En otros lenguajes esta tarea del refactoring puede ser muy engorroso y tomar mucho [...]

By: GrantPalin

GrantPalin — Mon, 22 Sep 2008 04:05:12 +0000

[...] Code Refactoring Guidelines [...]

By: Tom Dean

Tom Dean — Wed, 17 Sep 2008 20:14:35 +0000

@Lloyd

I believe he’s referring to object composition – i.e. creating a new class that combines the usage of several classes to perform it’s function, instead of having that class do it all itself.

By: Lloyd Moore

Lloyd Moore — Wed, 17 Sep 2008 16:30:00 +0000

I feel that some of these points are a little too abstract (excuse the pun). I refer mainly to the comment about extreme abstraction :- “Splitters can be lumped more easily than lumpers can be split”. I am not sure exactly what you mean by splitters – hopefully you are not referring to methods.

By: Generic collections in PHP | CodeUtopia

Generic collections in PHP | CodeUtopia — Wed, 17 Sep 2008 08:46:17 +0000

[...] while reading PHP::Impact’s refactoring guideline post I was reminded about [...]

By: Loic Hoguin

Loic Hoguin — Mon, 15 Sep 2008 12:37:23 +0000

That’s a pretty big list, but I feel it’s missing something (maybe I missed it). Ensure that tests are written for the code you’re going to refactor before you do it. That’s the only way to be sure you’re not going to change the behavior or add bugs.