Engineering the Future of Software
Feb 3–4, 2019: Training
Feb 4–6, 2019: Tutorials & Conference
New York, NY

Beyond accidental architecture

James Thompson (Mavenlink)
10:45am–12:15pm Tuesday, February 5, 2019
Fundamentals
Location: Trianon Ballroom
Secondary topics:  Best Practice, Overview
Average rating: ***..
(3.52, 27 ratings)

Who is this presentation for?

  • Software engineers and technical leaders

Level

Intermediate

Prerequisite knowledge

  • Experience working in a team environment

What you'll learn

  • Gain insight into how to help your team understand what software architecture is and how it can benefit from deliberate thinking
  • Learn how to help your team learn and grow

Description

Software systems always express some form of architecture. Many times those architectures reflect the mere circumstances and microtrends prevailing at various times. But long-term success doesn’t happen by accident. When approached deliberately, software architecture and design can produce benefits for teams in a variety of ways.

James Thompson demonstrates how to assess approaches and make decisions based on what matters to your team and your projects by answering the following guiding questions:

  • What is software architecture?
  • What decisions are architectural?
  • How do you discuss software architecture?
  • How do you document architectural decisions?
  • How do you encourage continued learning?

These questions give you a framework for thinking about how to do software architecture in a collaborative way. Software development is a collaborative effort, and software architecture should be also. Software architecture is something that every developer should be equipped and empowered to engage with—leading to a more collaborative way of developing and maintaining your software systems.

Photo of James Thompson

James Thompson

Mavenlink

James Thompson is a principal software engineer at Mavenlink, where he is committed to helping engineering teams become more deliberate in how they build software through developing strong learning cultures, principled engineering practices, and holistic architectural thinking. He has worked with web technologies since 2003.