Outstanding Chapter School Service Submissions
Thank you to our panel of judges for agreeing to help us out!
We hope that this set up will allow for a smooth and efficient judging process. Following each list of submissions is the rubric for judging that specific category. If you have any questions or concerns throughout this process, please do not hesitate to contact Sunita Jaswal, firstname.lastname@example.org.
Listed below is a brief description of what we expect, followed by each chapters' submission.
Outstanding Chapter School Service - 7 Chapter Submissions
Chapters should apply to the Outstanding Chapter School Service category if they have made significant contributions to their own schools through one major service project or a series of smaller projects. They should tell us about projects that have helped fellow students, their department, or their school in general. They should explain each project, how many people participated, and how it helped their school.
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.
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.