The travel guide to a software system
Imagine that tomorrow you started work on a new software system. What would you need to know to be productive? What information would help you orient yourself, make better decisions, and know that you're heading in the right direction? Patrick Kua uses the analogy of the travel guide to help you decide what to document in your software systems.
Talk Title | The travel guide to a software system |
Speakers | Patrick Kua (N26) |
Conference | O’Reilly Software Architecture Conference |
Conf Tag | Engineering the Future of Software |
Location | London, United Kingdom |
Date | October 16-18, 2017 |
URL | Talk Page |
Slides | Talk Slides |
Video | |
In today’s world of Agile software development, many teams interpret “working software over comprehensive documentation” as “no documentation.” However some level of documentation is essential for systems over their lifetime. Patrick Kua uses the analogy of the travel guide to help you decide what to document in your software systems, using a value-driven approach. Topics include: