How to rewrite software--and when not to.

Even knowing these rules, I broke one of the them. One you shouldn't ever break: don't rewrite your code from scratch.

Bibliographic Details
Published in:Computers in Libraries Vol. 29; no. 3; pp. 19 - 22
Main Author: Chudnov D
Format: Journal Article
Published: Information Today Inc. Mar2009
Online Access:View this record in EBSCOhost
fields @attributes:
  recordID: 1
pdfLink:
plink: https://search.ebscohost.com/login.aspx?direct=true&db=ccm&AN=105472462&site=ehost-live
header:
  @attributes:
    shortDbName: ccm
    uiTerm: 105472462
    longDbName: CINAHL Complete
    uiTag: AN
  controlInfo:
    bkinfo:
    dissinfo:
    jinfo:
      jid:
        10417915
        CLB
      jtl: Computers in Libraries
      issn: 10417915
      maglogo: N
    pubinfo:
      dt: Mar2009
      vid: 29
      iid: 3
      pid: 1730
      pub: Information Today Inc.
      place: Medford, New Jersey
    artinfo:
      ui:
        105472462
        2010217781
        105472462
      ppf: 19
      ppct: 3
      formats:
        fmt:
          – @attributes:
              type: T
          – @attributes:
              type: P
      tig:
        atl: How to rewrite software--and when not to.
      aug:
        au: Chudnov D
        affil: Office of Strategic Initiatives, Library of Congress; daniel.chudnov@gmail.com
      sug:
        subj:
          Software Design
          Writing Methods
          Programming Languages
      ab: Even knowing these rules, I broke one of the them. One you shouldn't ever break: don't rewrite your code from scratch.
      pubtype: Periodical
      doctype: Journal Article
      ougenre: Article
    language: English
    refInfo:
    holdings:
      @attributes:
        islocal: N