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.
Patrick Kua is the CTO of mobile bank N26, where he is building the engineering group that will change how retail banking works. Previously, Patrick was a principal technical consultant at ThoughtWorks in London. He is the author of three books: The Retrospective Handbook, Talking with Tech Leads, and most recently, Building Evolutionary Architectures. Patrick is a frequent conference speaker and blogger. He is passionate about bringing a balanced focus between people, organizations, and technology.
©2017, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org