Blogus Maximus

Rubbing people the wrong way since 1970...

  Home  |   Contact  |   Syndication    |   Login
  1268 Posts | 10 Stories | 1752 Comments | 1343 Trackbacks

News






Google My Blog

Catch me at: The List!


My InstallScript Utility Belt My Amazon Wishlist
My Standard Disclaimer

Men who feel strong in the justice of their cause, or confident in their powers, do not waste breath in childish boasts of their own superiority and querulous depreciation of their antagonists.
--James Russell Lowell, 1861



follow chrisgwilliams at http://twitter.com
My Blog Juice

Twitter












Archives

Post Categories

Image Galleries

Blogs

Code Camps

CTown Geeks

GDI+

Geeky Webcomics

High Geek

Magenic Blogs

Microsoft Blogs

My Articles

My Sites

My Sponsors

PodCasts

UG

XNA

The wikipedia defines refactoring as:

part of code maintenance which doesn't fix bugs or add new functionality. Rather it is designed to improve the understandability of the code or change its structure and design, and remove dead code, to make it easier for human maintenance in the future. In particular, adding new behavior to a program might be difficult with the program's given structure, so a developer might refactor it first to make it easy, and then add the new behavior.

Ok so... it turns out I've been doing this all along. I have a tendancy to self edit as I write. I do it in emails, blog posts and most certainly in my code. I don't think there's an untouched line of code left anywhere in HA! at this point. Thing is, I always just thought of it as "cleaning it up".

Also from the wikipedia: the term refactoring is often used to describe modifying source code without changing its external behavior, and is sometimes informally referred to as "cleaning it up".

Don't you love it when you find out you're following a good (best?) practice without even realizing it?


Oh and btw, this blog post was refactored at least 3 times before you ever saw it.

posted on Sunday, July 10, 2005 8:44 AM

Feedback

# re: Re-re-re-refactoring... 7/10/2005 12:12 PM Gerald Gibson
Generally refactoring is refering to rethinking an entire system after it has already been developed to version 1 or 2 or 3 etc. That is a bit different than editing the very sentence or class you are working on as you are creating it. Refactoring would mean after the entire project is complete you go back and take another look at all the pieces and see if any new realities that came about since you originally designed the system requires a newer and better design.

# re: Re-re-re-refactoring... 7/10/2005 4:00 PM BlogusMaximus
Thanks. I realize that, and perhaps my post wasn't clear. I've been known to go back to classes a few versions later and rework them in a more efficient manner while leaving the signature unaltered. The post was meant to be somewhat lighthearted.

Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification: