<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>ACM Queue - Development</title>
    <link>http://queue.acm.org/listing.cfm?item_topic=Development&amp;qc_type=topics_list&amp;filter=Development&amp;page_title=Development&amp;order=desc</link>
    <description />
    <item>
      <title>How Do Committees Invent? and Ironies of Automation</title>
      <link>http://queue.acm.org/detail.cfm?id=3395214</link>
      <description>The Lindy effect tells us that if a paper has been highly relevant for a long time, it's likely to continue being so for a long time to come as well. My first choice is "How Do Committees Invent?" Author Melvin E. Conway provides a lot of great material that led up to the formulation of the law that bears his name. My second choice is Lisanne Bainbridge's "Ironies of Automation." It's a classic treatise on the counterintuitive consequences of increasing levels of automation.</description>
      <category>Development</category>
      <pubDate>Wed, 15 Apr 2020 17:22:24 GMT</pubDate>
      <author>Adrian Colyer</author>
      <guid isPermaLink="false">3395214</guid>
    </item>
    <item>
      <title>Securing the Boot Process</title>
      <link>http://queue.acm.org/detail.cfm?id=3382016</link>
      <description>The goal of a hardware root of trust is to verify that the software installed in every component of the hardware is the software that was intended. This way you can verify and know without a doubt whether a machine's hardware or software has been hacked or overwritten by an adversary. In a world of modchips, supply chain attacks, evil maid attacks, cloud provider vulnerabilities in hardware components, and other attack vectors it has become more and more necessary to ensure hardware and software integrity.</description>
      <category>Development</category>
      <pubDate>Tue, 04 Feb 2020 13:47:02 GMT</pubDate>
      <author>Jessie Frazelle</author>
      <guid isPermaLink="false">3382016</guid>
    </item>
    <item>
      <title>Beyond the Fix-it Treadmill</title>
      <link>http://queue.acm.org/detail.cfm?id=3380780</link>
      <description>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.</description>
      <category>Development</category>
      <pubDate>Tue, 21 Jan 2020 13:23:16 GMT</pubDate>
      <author>J. Paul Reed</author>
      <guid isPermaLink="false">3380780</guid>
    </item>
    <item>
      <title>Managing the Hidden Costs of Coordination</title>
      <link>http://queue.acm.org/detail.cfm?id=3380779</link>
      <description>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.</description>
      <category>Development</category>
      <pubDate>Tue, 21 Jan 2020 13:15:43 GMT</pubDate>
      <author>Laura M.D. Maguire</author>
      <guid isPermaLink="false">3380779</guid>
    </item>
    <item>
      <title>Cognitive Work of Hypothesis Exploration During Anomaly Response</title>
      <link>http://queue.acm.org/detail.cfm?id=3380778</link>
      <description>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.</description>
      <category>Development</category>
      <pubDate>Tue, 21 Jan 2020 13:09:53 GMT</pubDate>
      <author>Marisa R. Grayson</author>
      <guid isPermaLink="false">3380778</guid>
    </item>
    <item>
      <title>Above the Line, Below the Line</title>
      <link>http://queue.acm.org/detail.cfm?id=3380777</link>
      <description>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.</description>
      <category>Development</category>
      <pubDate>Tue, 21 Jan 2020 13:03:31 GMT</pubDate>
      <author>Richard I. Cook</author>
      <guid isPermaLink="false">3380777</guid>
    </item>
    <item>
      <title>Revealing the Critical Role of Human Performance in Software</title>
      <link>http://queue.acm.org/detail.cfm?id=3380776</link>
      <description>Understanding, supporting, and sustaining the capabilities above the line of representation require all stakeholders to be able to continuously update and revise their models of how the system is messy and yet usually manages to work. This kind of openness to continually reexamine how the system really works requires expanding the efforts to learn from incidents.</description>
      <category>Development</category>
      <pubDate>Tue, 21 Jan 2020 12:56:47 GMT</pubDate>
      <author>David D. Woods, John Allspaw</author>
      <guid isPermaLink="false">3380776</guid>
    </item>
    <item>
      <title>Persistent Memory Programming on Conventional Hardware</title>
      <link>http://queue.acm.org/detail.cfm?id=3358957</link>
      <description>Driven by the advent of byte-addressable non-volatile memory, the persistent memory style of programming will gain traction among developers, taking its rightful place alongside existing paradigms for managing persistent application state. Until NVM becomes available on all computers, developers can use the techniques presented in this article to enjoy the benefits of persistent memory programming on conventional hardware.</description>
      <category>Development</category>
      <pubDate>Mon, 26 Aug 2019 13:17:55 GMT</pubDate>
      <author>Terence Kelly</author>
      <guid isPermaLink="false">3358957</guid>
    </item>
    <item>
      <title>Velocity in Software Engineering</title>
      <link>http://queue.acm.org/detail.cfm?id=3352692</link>
      <description>Software engineering occupies an increasingly critical role in companies across all sectors, but too many software initiatives end up both off target and over budget. A surer path is optimized for speed, open to experimentation and learning, agile, and subject to regular course correcting. Good ideas tend to be abundant, though execution at high velocity is elusive. The good news is that velocity is controllable; companies can invest systematically to increase it.</description>
      <category>Development</category>
      <pubDate>Mon, 29 Jul 2019 13:17:00 GMT</pubDate>
      <author>Tom Killalea</author>
      <guid isPermaLink="false">3352692</guid>
    </item>
    <item>
      <title>Surviving Software Dependencies</title>
      <link>http://queue.acm.org/detail.cfm?id=3344149</link>
      <description>Software reuse is finally here, and its benefits should not be understated, but we've accepted this transformation without completely thinking through the potential consequences. The Copay and Equifax attacks are clear warnings of real problems in the way software dependencies are consumed today. There's a lot of good software out there. Let's work together to find out how to reuse it safely.</description>
      <category>Development</category>
      <pubDate>Mon, 08 Jul 2019 11:06:54 GMT</pubDate>
      <author>Russ Cox</author>
      <guid isPermaLink="false">3344149</guid>
    </item>
  </channel>
</rss>

