view issue

A Conversation with Steve Bourne, Eric Allman, and Bryan Cantrill: In part one of a two-part series, three Queue editorial board members discuss the practice of software engineering.

July 1, 2008

Topic: Development

  • View Comments
  • Print

Related:

J. Paul Reed - Beyond the Fix-it Treadmill
Given that humanity’s study of the sociological factors in safety is almost a century old, the technology industry’s post-incident analysis practices and how we create and use the artifacts those practices produce are all still in their infancy. So don’t be surprised that many of these practices are so similar, that the cognitive and social models used to parse apart and understand incidents and outages are few and cemented in the operational ethos, and that the byproducts sought from post-incident analyses are far-and-away focused on remediation items and prevention.


Laura M.D. Maguire - Managing the Hidden Costs of Coordination
Some initial considerations to control cognitive costs for incident responders include: (1) assessing coordination strategies relative to the cognitive demands of the incident; (2) recognizing when adaptations represent a tension between multiple competing demands (coordination and cognitive work) and seeking to understand them better rather than unilaterally eliminating them; (3) widening the lens to study the joint cognition system (integration of human-machine capabilities) as the unit of analysis; and (4) viewing joint activity as an opportunity for enabling reciprocity across inter- and intra-organizational boundaries.


Marisa R. Grayson - Cognitive Work of Hypothesis Exploration During Anomaly Response
Four incidents from web-based software companies reveal important aspects of anomaly response processes when incidents arise in web operations, two of which are discussed in this article. One particular cognitive function examined in detail is hypothesis generation and exploration, given the impact of obscure automation on engineers’ development of coherent models of the systems they manage. Each case was analyzed using the techniques and concepts of cognitive systems engineering. The set of cases provides a window into the cognitive work "above the line" in incident management of complex web-operation systems.


Richard I. Cook - Above the Line, Below the Line
Knowledge and understanding of below-the-line structure and function are continuously in flux. Near-constant effort is required to calibrate and refresh the understanding of the workings, dependencies, limitations, and capabilities of what is present there. In this dynamic situation no individual or group can ever know the system state. Instead, individuals and groups must be content with partial, fragmented mental models that require more or less constant updating and adjustment if they are to be useful.


In part one of a two-part series, three Queue editorial board members discuss the practice of software engineering. In their quest to solve the next big computing problem or develop the next disruptive technology, software engineers rarely take the time to look back at the history of their profession. What’s changed? What hasn’t changed? In an effort to shed light on these questions, we invited three members of ACM Queue’s editorial advisory board to sit down and offer their perspectives on the continuously evolving practice of software engineering.



Back to top

Comments

(newest first)

Sergei Kukolev | Fri, 20 Feb 2009 13:24:43 UTC

I am supposed to initiate a new retrospective project for the Norton Commander functionality in new terms of

dynamic structures semantics {inf.by/subject} to represent a new terms functionality of the Norton

Commander file manager system and program interface design with mean to implement a new kind of basic

functionality on its basis. This is kind of programming interface to represent the current state of the dynamic structures in use like

program elements and files altogether. This is a classic style interface of the Norton Commander file

manager. It may present a programm data in its dynamics. Just imagine yourself the Norton Commander interface with Kubik Rubik dynamics. Rotation of the "Norton

Kubik" structure changes the current content and state of Norton Commander interface. Thus simple to gain

an incredible functionality of the dynamic structures with one click by Norton Commander remake!

Kinda Kubik Rubik Norton Commander. Hybrid loopback.


Leave this field empty

Post a Comment: