BEGIN:VCALENDAR
VERSION:2.0
PRODID:IEEE vTools.Events//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/Denver
BEGIN:DAYLIGHT
DTSTART:20230312T030000
TZOFFSETFROM:-0700
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:MDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20231105T010000
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:MST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20231024T175127Z
UID:0AE4E03A-75CF-44EC-8C8A-6BD1DF479E33
DTSTART;TZID=America/Denver:20231023T160000
DTEND;TZID=America/Denver:20231023T172000
DESCRIPTION:What is the secret to software engineering at Google? Over the 
 years\, we’ve come to recognize three key principles that guide our prac
 tices and decisions: Time\, Scale\, and Tradeoffs. We recently published a
  book with O'Reilly on those principles\, and we'll share the key ideas he
 re.\n\nSoftware engineering and programming are related but different prob
 lems. If programming is about producing code\, software engineering is abo
 ut maintaining that code for the duration of its usefulness. It is about t
 he practices\, policies\, and decisions that support robust and reliable c
 ode. It is about building for growth and for the ability to manage change\
 , sustainably.\n\nAt Google\, we have learned many lessons related to the 
 sustainability of software. Google arguably maintains one of the largest c
 odebases ever. The expected lifespan of the codebase is at least another c
 ouple of decades. We’ve needed to figure out how to operate at a scale p
 reviously unattempted for a timespan longer than most others have consider
 ed. Learning from the difficulties that we have encountered along the way 
 while wrangling with this unprecedented problem\, we have developed practi
 ces around time\, scaling\, and evidence-based decision making. This is wh
 at has enabled us to operate as we do.\n\nThis talk will explore the theme
 s of time\, scale\, and tradeoffs in the context of sustainable software e
 ngineering. We will discuss the impact that each of these factors has on t
 he process of software development and maintenance and how Google has shap
 ed its engineering practices to take these principles into account.\n\nCal
 gary\, Alberta\, Canada\, T3E 6K6\, Virtual: https://events.vtools.ieee.or
 g/m/377684
LOCATION:Calgary\, Alberta\, Canada\, T3E 6K6\, Virtual: https://events.vto
 ols.ieee.org/m/377684
ORGANIZER:yamannejad@mtroyal.ca
SEQUENCE:20
SUMMARY:Software Engineering Principles
URL;VALUE=URI:https://events.vtools.ieee.org/m/377684
X-ALT-DESC:Description: <br /><p dir="ltr">What is the secret to software e
 ngineering at Google? Over the years\, we&rsquo\;ve come to recognize thre
 e key principles that guide our practices and decisions: Time\, Scale\, an
 d Tradeoffs. We recently published a book with O'Reilly on those principle
 s\, and we'll share the key ideas here.</p>\n<p dir="ltr">Software enginee
 ring and programming are related but different problems. If programming is
  about producing code\, software engineering is about maintaining that cod
 e for the duration of its usefulness. It is about the practices\, policies
 \, and decisions that support robust and reliable code. It is about buildi
 ng for growth and for the ability to manage change\, sustainably.&nbsp\;</
 p>\n<p dir="ltr">At Google\, we have learned many lessons related to the s
 ustainability of software. Google arguably maintains one of the largest co
 debases ever. The expected lifespan of the codebase is at least another co
 uple of decades. We&rsquo\;ve needed to figure out how to operate at a sca
 le previously unattempted for a timespan longer than most others have cons
 idered. Learning from the difficulties that we have encountered along the 
 way while wrangling with this unprecedented problem\, we have developed pr
 actices around time\, scaling\, and evidence-based decision making. This i
 s what has enabled us to operate as we do.</p>\n<p dir="ltr">This talk wil
 l explore the themes of time\, scale\, and tradeoffs in the context of sus
 tainable software engineering. We will discuss the impact that each of the
 se factors has on the process of software development and maintenance and 
 how Google has shaped its engineering practices to take these principles i
 nto account.</p>
END:VEVENT
END:VCALENDAR