The Business of Software In Praise of Bad Programmers.

The author discusses the advantages of a team approach in software programming. He mentions his experience of managing a team that included a low-level programmer. The team defined the metrics for success necessary for each team member. Although the programmer did not measure up, the manager found t...

Descripción completa

Detalles Bibliográficos
Publicado en:Communications of the ACM Vol. 53; no. 1; pp. 35 - 37
Autor principal: Armour, Phillip G.
Formato: Artículo
Publicado: Association for Computing Machinery Jan2010
Materias:
Acceso en línea:Ver este registro en EBSCOhost
fields @attributes:
  recordID: 1
pdfLink:
plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=47220606&site=ehost-live
header:
  @attributes:
    shortDbName: hlh
    uiTerm: 47220606
    longDbName: Humanities International Complete
    uiTag: AN
  controlInfo:
    bkinfo:
    jinfo:
      jid:
        00010782
        ACM
      jtl: Communications of the ACM
      issn: 00010782
      maglogo: N
    pubinfo:
      dt: Jan2010
      vid: 53
      iid: 1
      pid: 68
      pub: Association for Computing Machinery
    artinfo:
      ui:
        47220606
        10.1145/1629175.1629190
      ppf: 35
      ppct: 2
      formats:
      tig:
        atl: The Business of Software In Praise of Bad Programmers.
      aug:
        au: Armour, Phillip G.
        affil: Senior consultant, Corvus International Inc., Deer Park, IL.
      su:
        Computer programmers
        Management of teams in the workplace
        Work sharing
        Employee reviews
        Group decision making
        Organizational structure
      sug:
        subj:
          Computer programmers
          Management of teams in the workplace
          Work sharing
          Employee reviews
          Group decision making
          Organizational structure
      ab: The author discusses the advantages of a team approach in software programming. He mentions his experience of managing a team that included a low-level programmer. The team defined the metrics for success necessary for each team member. Although the programmer did not measure up, the manager found that the team improved when they had to define their process to support their weaker team member. He mentions that the team was able to overcome individual limitations while not sacrificing individuality and creativity.
      pubtype: Periodical
      doctype: Article
      src: R
    language: English
    refInfo:
    copyright:
      @attributes:
        flag: Y
      dt:
        @attributes:
          year: 2010
    holdings:
      @attributes:
        islocal: N