Engineering the Future of Software
November 13–14, 2016: Training
November 14–16, 2016: Tutorials & Conference
San Francisco, CA

Schedule: Fundamentals sessions

1:30pm–5:00pm Monday, 11/14/2016
Location: California West Level: Beginner
Pramod Sadalage (ThoughtWorks)
Average rating: ****.
(4.50, 2 ratings)
Pramod Sadalage discusses evolutionary database design, database refactoring patterns, and different implementation techniques to enable blue-green deployments, allow for legacy applications to work with fast changing database, and enable teams to effectively refactor the database to fulfill the changing needs of the organization. Read more.
10:45am–12:15pm Tuesday, 11/15/2016
Location: California East Level: Beginner
Nathaniel Schutta (Pivotal)
Average rating: ****.
(4.56, 9 ratings)
Developers focus on functional requirements, but once you step into the architect role, your world is increasingly inhabited by the "-ilities"—the nonfunctional or quality attributes of a software system. But which "-ilities" matter and which don't? Nathaniel Schutta explores approaches to architectural problems and explains how to best document the inevitable decisions we arrive at. Read more.
2:15pm–3:05pm Tuesday, 11/15/2016
Location: California West Level: Intermediate
Mridul Mishra (Fidelity Investments), Tim Poole (Fidelity Investments)
Average rating: ***..
(3.00, 6 ratings)
Behavioral finance, a new field of financial theory, really means that people are not the logical, rational wealth creators that traditional financial theories proposed. Mridul Mishra and Tim Poole adapt this concept to architecture, explaining why those trying to influence architecture and technology decisions need to take the human side of decision makers into account. Read more.
3:50pm–4:40pm Tuesday, 11/15/2016
Location: California East Level: Intermediate
Yurii Rashkovskii (Etcetera Labs, Inc.)
Yurii Rashkovskii shares a set of practical of approaches to designing event-sourcing-based systems, including a method of building the state of the world that uses a "lazy first" approach. This approach suggests that we don't know what the state of the world should include up front and therefore should defer this decision until the very end. Read more.
10:45am–12:15pm Wednesday, 11/16/2016
Location: Tower Salon A Level: Intermediate
Kurtis Kemple (Major League Soccer)
Average rating: ****.
(4.00, 8 ratings)
JavaScript is replacing Java, Ruby, and .NET as the technology of choice for companies that want to build enterprise software faster and with fewer resources. Kurtis Kemple offers an overview of enterprise JavaScript applications at every level of the stack and discusses how to secure, integrate, test, store, monitor, and deploy them. Read more.
1:15pm–2:05pm Wednesday, 11/16/2016
Location: California East Level: Beginner
Nancy Nunes (Architects Who Code)
Average rating: **...
(2.50, 10 ratings)
Software architecture can be flexible enough for product-line scalability and product evolution. Nancy Nunes covers three programming-language and development-process independent instruments that are key to creating, manipulating, and maintaining a software architecture that can yield lean and flexible software products. Read more.
2:15pm–3:05pm Wednesday, 11/16/2016
Location: Tower Salon A Level: Beginner
Average rating: ****.
(4.00, 4 ratings)
Data is available from an incredible number of sources in an endless number of formats. Data science deals with the extraction of valuable insights from this jumble in the form of attractive visualizations. Walking you through several examples using practical tools and tricks, Margriet Groenendijk presents a typical workflow that offers a basic introduction to data science. Read more.
4:50pm–5:40pm Wednesday, 11/16/2016
Location: Georgian Level: Beginner
Jayson DeLancey (HERE Technologies)
Average rating: ****.
(4.67, 3 ratings)
Jayson DeLancey offers a review of the systems architectures used in creating ebooks, animating movies, cloud computing, robotics, and other really important things and demonstrates how the behavior and structure of the organization itself has unexpected impacts on how technical architectures evolve. Read more.