x

Main chapters

  1. LimeSurvey Cloud vs LimeSurvey CE
  2. LimeSurvey Cloud - Quick start guide
  3. LimeSurvey CE - Installation
  4. How to design a good survey (Guide)
  5. Getting started
  6. LimeSurvey configuration
  7. Introduction - Surveys
  8. View survey settings
  9. View survey menu
  10. View survey structure
  11. Introduction - Questions
  12. Introduction - Question Groups
  13. Introduction - Surveys - Management
  14. Survey toolbar options
  15. Multilingual survey
  16. Quick start guide - ExpressionScript
  17. Advanced features
  18. General FAQ
  19. Troubleshooting
  20. Workarounds
  21. License
  22. Version change log
  23. Plugins - Advanced
 Actions

Code quality guide

From LimeSurvey Manual

Revision as of 20:45, 2 April 2021 by Ollehar (talk | contribs) (Created page with "DRAFT == Prologue == # Be risk aware. # Be humble. LimeSurvey was made by developers from all over the world, with different age, education and experience. # Performance mat...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

DRAFT

Prologue

  1. Be risk aware.
  2. Be humble. LimeSurvey was made by developers from all over the world, with different age, education and experience.
  3. Performance matters sometimes
  4. It's harder to read code than to write code
  5. Stress affects quality

Quality

What is quality? Which aspects of quality can we measured?

Idiomatic code is more readable than non-idiomatic code. What's idiomatic depends on which context or domain you work in. We work in PHP and web application development, and have other idioms than in functional programming.