The Digital Library : 2010 POD Titles

2010 Print on Demand Proceeding Titles

Title ISBN Amazon Barnes & Noble
ASE 2010 978-1-4503-0116-9 POD from Amazon POD from Barnes & Noble
CGO 2010 978-1-60558-635-9 POD from Amazon POD from Barnes & Noble
EC 2010 978-1-60558-822-3 POD from Amazon POD from Barnes & Noble
IHI 2010 978-1-4503-0030-8 POD from Amazon POD from Barnes & Noble
IMC 2010 978-1-4503-0057-5 POD from Amazon POD from Barnes & Noble
ISCA 2010 978-1-4503-0052-0 POD from Amazon POD from Barnes & Noble
LCTES 2010 978-1-6055-8953-4 POD from Amazon POD from Barnes & Noble
OOPSLA 2010 978-1-4503-0203-6 POD from Amazon POD from Barnes & Noble
PACT 2010 978-1-4503-0178-7 POD from Amazon POD from Barnes & Noble
SoCG 2010 978-1-4503-0016-2 POD from Amazon POD from Barnes & Noble
SIGAda 2010 978-1-4503-0027-8 POD from Amazon POD from Barnes & Noble
SIGCSE 2010 978-1-6055-8885-8 POD from Amazon POD from Barnes & Noble
SIGDOC 2010 978-1-4503-0403-0 POD from Amazon POD from Barnes & Noble
SIGUCCS 2010 978-1-4503-0003-2 POD from Amazon POD from Barnes & Noble
SPAA 2010 978-1-4503-0079-7 POD from Amazon POD from Barnes & Noble
SPLASH 2010 978-1-4503-0240-1 POD from Amazon POD from Barnes & Noble
STOC 2010 978-1-6055-8817-9 POD from Amazon POD from Barnes & Noble

Last updated December 9, 2013

The DevOps Phenomenon

ACM Queue’s “Research for Practice” consistently serves up expert-curated guides to the best of computing research, and relates these breakthroughs to the challenges that software engineers face every day. This installment of RfP is by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald, and Helmut Krcmar. Titled “The DevOps Phenomenon,” this RfP gives an overview of stories from across the industry about software organizations overcoming the early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between their software and operations teams, faster delivery times for new software features, and achieving a higher level of stability.

ACM Case Studies

Written by leading domain experts for software engineers, ACM Case Studies provide an in-depth look at how software teams overcome specific challenges by implementing new technologies, adopting new practices, or a combination of both. Often through first-hand accounts, these pieces explore what the challenges were, the tools and techniques that were used to combat them, and the solution that was achieved.

Why I Belong to ACM

Hear from Bryan Cantrill, vice president of engineering at Joyent, Ben Fried chief information officer at Google, and Theo Schlossnagle, OmniTI founder on why they are members of ACM.