Session Description
Why bother writing comments or documentation or following standards in the back end; especially if all the users ever see is the user interface? Now ask yourself another question: if you are hit by a bus, will your clients, colleagues, or development teammates be able to understand the code you have written to a degree that they can complete the project without you? Even in the rare cases where the answer is “yes,” inheriting your undocumented code may well jeopardize the project by delaying the schedule and putting it over budget. The simple act of following standards and creating documentation will make you a better programmer and will also help you to remember design choices you may have made years ago. What exactly are the things you should document? This session will help you make wise choices about the type of documentation to keep for a system, and also to create documentation that will actually help you and others understand your solutions.
Products & Technologies
- FileMaker Pro
What You Will Learn
- Learn to comment an entire solution to remember what you did months or years in the past
- User documentation is just as important for the developer as for the users. Make it work for you!
- All choices are made for good reasons, those reasons may not be true anymore, and what were those reasons?
- Give yourself the discipline to be a better developer
Recent Comments