Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21b4e900ab8376a

Jump to content

Chief programmer team

From Wikipedia, the free encyclopedia

A chief programmer team is a programming team organized in a star around a "chief" role, granted to the software engineer who understands the system's intentions the best. Other team members get supporting roles.[1]

The concept is similar to that of a surgical team in which a surgeon who performs the operation is supported by medical staff such as an anaesthetist and nurses.[1] Fred Brooks describes the concept in detail in The Mythical Man-Month,[2] as proposed by Harlan Mills[3] in 1971.

Team structure

[edit]

The team consists of people. Various roles have been defined for team members, the following are taken from Brooks.[2]

  • Program Clerk: responsible for all project technical records.
  • Toolsmith: builds and supports tools used by developers.
  • Language Lawyer: has in-depth expertise in the language(s) used to develop the project.

In this arrangement the chief programmer and backup programmer actually work on the problem. The remaining team members provide "all conceivable support."

References

[edit]
  1. 1 2 Doug Bell (2005), Software engineering for students: a programming approach, ISBN 9780321261274
  2. 1 2 Brooks, Jr., Frederick P. (1975). The Mythical Man-Month. Addison-Wesley Publishing Company. pp. 32––35.
  3. Mills, H. (1971), "Chief programmer teams, principles, and procedures", IBM Federal Systems Division Report FSC71-5108, Gaithersburg, Md.
[edit]