Extreme measures.

Part of a special section on technological innovation. “Extreme programming” (XP), a software design approach advocating that more method equals less confusion, is growing in popularity. XP was developed in 1996, when software developer Kent Beck was asked by car maker Chrysler to save a project t...

Descripción completa

Detalles Bibliográficos
Publicado en:Economist Vol. 357; pp. 7 - 9
Formato: Artículo
Publicado: Economist Newspaper Limited 12/9/2000
Acceso en línea:Ver este registro en EBSCOhost
fields @attributes:
  recordID: 1
pdfLink:
plink: https://search.ebscohost.com/login.aspx?direct=true&db=ssf&AN=507738359&site=ehost-live
header:
  @attributes:
    shortDbName: ssf
    uiTerm: 507738359
    longDbName: Social Sciences Full Text (H.W. Wilson)
    uiTag: AN
  controlInfo:
    bkinfo:
    jinfo:
      jid:
        00130613
        ECO
      jtl: Economist
      issn: 00130613
      maglogo: N
    pubinfo:
      dt: 12/9/2000
      vid: 357
      pid: 161
      pub: Economist Newspaper Limited
    artinfo:
      ui: 507738359
      ppf: 7
      ppct: 2
      formats:
      tig:
        atl: Extreme measures.
      aug:
      su: eXtreme programming
      sug:
        subj: eXtreme programming
      ab: Part of a special section on technological innovation. “Extreme programming” (XP), a software design approach advocating that more method equals less confusion, is growing in popularity. XP was developed in 1996, when software developer Kent Beck was asked by car maker Chrysler to save a project that it had scrapped. For this project, Beck designed a set of directions to keep code “elegantly written.” However, some of these rules have generated controversy, particularly the one that specifies that programmers work in pairs, on one terminal, on each bit of code. Critics argue that this rule will lead to inefficiency, with the pairing of programmers with mismatched capabilities. Nonetheless, proponents of XP believe that with the rotation of people to different tasks and pair-programming there is the benefit of having an easy-to-maintain code, with minimum expense, after only a few years.
      pubtype: Periodical
      doctype: Article
      src: R
    language: English
    refInfo:
    copyright:
      @attributes:
        flag: N
    holdings:
      @attributes:
        islocal: N