To create a quality application, you need to make your code readable, understandable, and maintainable for all developers who might work on the project in the future. To do this, you need to communicate how your code works and how the application architecture is structured.
In this course, you’ll learn the best practices to make your code self-documenting, see how to create good documentation and publish it online, and find out how to document an API.
In the second part, we’ll look at some best practices for creating architecture documentation and the points you need to consider.
Your teachers on this course are Max Wardeh and Francis Bock.
Max Wardeh is a university lecturer and web development consultant. He has been working in web development for over 20 years.
Francis Bock is deputy director of a European project providing geospatial services. He has taught back-end development at Gustave Eiffel University and formerly held the role of CIO for a French government department.
So, you want to provide the best possible experience for your colleagues when using your code and its documentation? Then let’s get started on the first chapter!
Learning outcomes
Contributors
Instructor
Created by
