Welcome! We’re excited to have you on our team!
You play a crucial role in our success, and together, we can achieve great things. Our team’s mission is to create exceptional software that enhances both productivity and happiness. We develop a variety of products, including games, productivity tools, and maintenance software.
To join our team, you need to be selected by our leadership team. If you were hired through platforms such as Fiverr, Upwork, or others, please be aware that the rules and regulations of that platform are part of your contract with us.
Repo access
Full contract repo access
Full Contract: Please ensure you have signed the full contract before accessing any repository. We use Unity Cloud, GitHub, and our internal SVN server, depending on the project you are working on. If you have received a welcome package with login credentials, please use them.
Freelancer repo access
If you joined through a platform like fiverr or upwork, you will access the repository via alternate means, such as Google Drive links or our FTP server. Please download the necessary files and, after completing your assignment, send us the results via a secure method (e.g., Google Drive). Make sure to delete the link after we’ve downloaded the data.
Iterations
Even if iterations are not part of your original assignment, please don’t hesitate to reach out if something is unclear or if issues arise during your work. It’s essential to stop and contact us for clarification. If you think additional iterations are needed, always feel free to request them. The quality of the final product is our top priority. If we feel improvements are needed, we will request additional iterations.
Code Guidelines
- Clean Code: Always follow clean coding practices.
- Functionality: A function should do only one thing (Single Responsibility Principle).
- Naming Conventions:
- Avoid vague names like i, x, age. Instead, use descriptive names like counterI, counterX, ageOfUser, ageOfCustomer.
- Function names should be clear, like CalculatesAgeOfUser(), not just Calc().
- Performance: Avoid using Update() unnecessarily.
- Empty Functions: Never leave empty functions in the code.
- Comments: Use comments for anything unclear. However, strive to improve naming where possible so comments are not necessary.
- Unit Tests: Unit tests are always recommended, but only required if specified in your contract. They always contribute to quality rating points.
- To-Dos: If there are any pending tasks, mark them with a comment (//TODO: Description).
Delivery
- Direct Repo Access: If you have direct access to the repository, please deliver your work directly through it.
- Alternative Delivery: If not, use a secure method like Google Drive, and delete the link once we’ve downloaded the files.
- Always include a brief description with your delivery. For repo deliveries, use the commit comment. Otherwise, send us a short summary of the work completed.
Error reporting
If you find errors outside of your assignment, please report them directly to your contact. Good error reports will count towards your quality rating.
Rating
We maintain internal ratings for all entities we collaborate with, with a strong focus on the quality of the delivered product and the working processes.