This FileMaker training video discusses the top 7 reasons not to comment your solution.
This is part 1 of 2 videos. The second video will demonstrate the best practices and options for commenting.
Commenting or properly documenting is not just confined to a script. There are numerous places where notation can be used.
The additional notes and descriptions are not just for developers. Layout design, table structure, fields names, and other specific tools can make the entire commenting process easier for both the creator and the end user.
► PCI WEBSITE: https://www.productivecomputing.com/
► ONLINE UNIVERSITY: https://www.productivecomputinguniversity.com/
► TWITTER: https://twitter.com/prodcomp
► FACEBOOK: https://www.facebook.com/productivecomputing/
► LINKEDIN: https://www.linkedin.com/company/productive-computing-inc.
Please subscribe if you like this content or want to stay informed on more Productive Computing and FileMaker training videos.
► Auto Subscribe: https://youtube.com/c/ProductiveComputing?sub_confirmation=1
Thanks for watching!
I have always struggled to find the right balance of commenting too much or not enough. This helped put the big picture in perspective so that I am not wasting time on the wrong aspect of developing a solution.
✅ Online training for your future– FileMaker Certification Preparation: http://www.ProductiveComputingUniversity.com
✅ See FileMaker 18 Features playlist: https://www.youtube.com/playlist?list=PLLFSxz1yusVq4Zn2DO_hwgB4fvtd6gqet
✅ See FileMaker 17 Features playlist: https://www.youtube.com/playlist?list=PLLFSxz1yusVoKVrqoi6VwfmUYpQUjFem9
Hahaha… you tricked me… I was wondering why you’d publish a video saying not to document a solution… still giggling