Refactoring: Improving the Design of Existing Code

  • Comments posted to this topic are about the content posted at Improving the Design of Existing Code.

  • I haven't read this particular book, but my comment is that a book from a different discipline can provide a useful perspective that is applicable to the SQL discipline.

    For example, I've been working through the Ivor Horton book "Beginning Visual C++4" off and on for the past 3 years (I'm not a slow reader I've got 3 kids).

    From this I've picked up hints on "Hungarian notation", that is prefixing variables and objects with a type identifier which is directly related to recent articles on this site.

    It has also made me a better programmer because I have a greater appreciation of objects and their life cycle.

    Application development books (not the teach yourself in 'x' days/hours books) are good because they tend to slant towards what people actually want to use databases for and therefore they give hints on the areas that you should target your skills.

  • Good to see a book about this, a topic that's been around some time, but never formalised. Not aware of any formal methodology for safely changing code once it's in a working system, so this sounds like a welcome addition to any conciencious coder's library. Code Complete (MS Press, ISBN: 1556154844) by Steve McConnell is also an excellent work which would probably complement this one. Although it concentrates more on getting the code right in the first place, many of the same principles apply, though it does not present a method for safely re-writing code. Maybe one to send to your third party application provider when your new $100,000 app. starts performing like a dog 😉

    Jon Reade


    Jon

  • Thanks for the comments so far, didnt know what reaction to expect! David one note, MS in its wisdom is moving away from Hungarian in .Net.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

  • What are they using instead of Hungarian?

    Considering the battle to get developers to adhere to standards I don't relish the idea of changing just because MS don't feel like it anymore!

    I would like to here a convincing argument for changing it.

    If it ain't broke.......

  • Dont know if I can present one yet. I'll see if I can find something where they outline their reasons. I kinda use hungarian, mostly for controls on VB forms. Even pre-.Net they recommended not using hungarian for class names or public methods of classes. Dont know that there is a compelling reason to switch if you have a standard in place.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply