At Povio we strive for quality and constant improvement. For these reasons we prepared a set of guidelines and for the same reasons, these guidelines are being constantly improved upon. These guidelines are not the only and best solution to software development. Nonetheless, they should either be respected on our projects or we should know and have good reason for why they are not. This is a group effort and anyone can contribute, so feedback is very welcome and much appreciated.

You should read and follow the general guidelines and the guidelines for the respective technology you are working with.

General Guidelines

General guidelines are applicable to most of our projects and are language-agnostic.

• Infrastructure
• Git and Github
• IDEs / Text Editors

Code Guidelines

We want to produce code that is readable, testable and maintainable. Code that is written with error prevention, performance and scalability in mind. In short, quality code. With that goal in mind, we put together a collection of guidelines for the technologies that we use the most.

• Android
• iOS
• Java
• JavaScript
• Ruby on Rails
• Slicing

Quality Assurance Guidelines

Quality Assurance or QA is a integral part of the software development process and plays a crucial role in ensuring the quality of products. The Quality Assurance guidelines describe how we tackle tasks such as ensuring that products meet all requirements and standards, finding and preventing mistakes, defects and other unwanted issues, reporting issues and ensuring they have been resolved successfully.

• Quality Assurance