This paper discusses the importance of coding standards and good practices in software projects, with a specific focus on Prolog programming. The authors acknowledge the lack of widely accepted standards and practices in the Prolog community and aim to provide immediate guidelines for code layout, naming conventions, documentation, use of Prolog features, program development, debugging, and testing. The guidelines are supported with rationale and illustrations of the pros and cons for each alternative. The paper also emphasizes the need for a project-specific coding standard, considering various factors and criteria. The submission history indicates multiple revisions of the paper.
https://arxiv.org/abs/0911.2899