With the continued popularity of the Animal Crossing franchise and the growing membership of ACC, the Site Owner, jader201, decided to form two groups designated with the task of brainstorming various ideas for improving the site as well as making these ideas a reality. These two groups, the Researchers and the Developers, are collectively recognized by these combinable icons which reflect their inter-dependant relationship.
ACC Developers can be identified by the icon which is located to the left of their username.
Initially, Developers work alongside the Researchers and other Staff to discuss ideas for improving and updating the site. With their coding ability, Developers bring a unique perspective to discussions and also help to steer ideas because they know what is feasible within the existing code. This enables other Staff to understand more thoroughly whether a discussion should be pursued or continued at a later time.
Out of all the Staff, only Developers have access to the website's code. When an idea has support and is approved, it is their job to implement it. They have their own board for discussing any issues arising from their work and also have sole access to an environment in which they can create changes to the site code.
Members who feel they have they have the skills to become part of the Development Team initially submit an application form. The ACC Staff consider a number of factors when assessing an application, some of which are listed below. Therefore, prior to submitting an application, it's prudent to read and understand both the recruitment factors and the responsibilities for the role.
Age -- Applicants should be a minimum of 13 years old but there is no upper age restriction. We aim to have a good balance of younger and older members, with varying degrees of experience.
Site Activity -- A person who has been active for a while can more easily assess which new features would be relevant to the Community and which features are in need of updating. Thus applications tend to be considered only from those who have been consistently active on ACC for at least 9 months.
Communication -- Developers need to have good, clear and precise communication with everyone. Applicants should therefore have a history of both expressing their ideas well and responding to others constructively on the public boards.
Responsibility -- Adhering to site rules and respecting others will help to show that the applicant can be responsible and is likely to be trustworthy. This is important as Developers are required to take responsibility for certain tasks and are expected not to divulge any information to the Community which has been read or discussed on Staff boards.
Maturity -- Applicants need to remain calm and composed at all times. Although communication is a crucial factor, applicants are also assessed on their responses when faced with critique or opposition to their opinions. Accepting that other people can have different but equally valid points, is seen as a sign of maturity.
Creativity -- Applicants should have original and interesting ideas, that fit in with the purpose of the site.
Teamwork -- Applicants need to demonstrate the ability to build upon ideas proposed by others, rather than only concern themselves with their own ideas and topics.
Once recruited into the team, Developers are expected to fulfill the following duties:
Feature Discussions -- Developers are required to actively participate in discussions on potential features by offering feedback, suggestions and alternatives.
Monitor Site Support Board -- The Site Support board is where the Community requests help and informs the Staff of site errors. Some of the topics cover technical issues and legitimate concerns that only Developers are able to provide solutions for. Therefore, monitoring of this board is vital to the Developer role.
Monitor Site Suggestions Board -- The Site Suggestions board is where the Community post suggestions and offer critique about the site. Although this board is monitored mostly by Researchers, the Developers also need to occasionally add their unique insight.
Add New Features -- Developers work collaboratively with the other Staff to implement new features and ideas into the site. They are expected to keep the site user-friendly, fresh and innovative.
Update Existing Content -- Although new features are always a bonus, it's important to review existing content and refresh it, as well as fix bugs and faults. Developers are required to be adaptable and able to work on small fixes as well as larger projects such as those required whenever there is a new release of Animal Crossing.
Test Features -- Once features are individually coded, Developers are expected to test their own work and fix any code errors. All features are then merged to ensure there are no conflicts when combined. This Dev-Testing can highlight errors and Developers are expected to work as a team, suggesting solutions where necessary. Once this stage is error free, all features are merged to a live version of the site to ensure that there are no conflicts with existing site features. This Beta-Testing stage involves all Staff because often, those not involved in coding find it easier to suggest visual and mechanical amendments or improvements. This phase also brings more errors to the fore which Developers are expected to remedy.
Developer Team Leads
A group of several Developers submitting changes can cause multiple code conflicts. In order to minimize these, two Developers are also given the position of Developer Team Leads and they act as gatekeepers for all code submissions. It is their job to merge every code change into one usable codebase by checking that features are working correctly both individually and in combination with each other. Any features containing errors are sent back to the Developers who worked on them.
Team Leads also make decisions on whether features are ready for Dev-Testing or Beta-Testing, plus they decide when each testing phase is complete. When Team Leads confirm that Beta-Testing is free from errors and further amendments are not required, the Site Owner jader201 makes the final checks. Having verified all work, he then merges the changes to the live site.
For being part of Staff, Developers have the following privileges:
A cool icon next to their name!
Access to their own board for the purpose of brainstorming and helping each other.
Their own unique environment in which to work on their code changes.
Access to Dev-Test and Beta-Test various features.
Access to the inner workings of ACC.
No restrictions on the quantity of posts or threads they can submit.
Access to avatars reserved only for Staff.
Ability to view how many people have flagged a thread.
Access to their own Archived Threads.
Whilst the Staff are not always looking to add more Developers to the team, applications are welcome at any time. However, please understand that these won't be considered until we intend to recruit.
If you feel that you have the skills required and can fulfill the duties expected of a Developer, please see below for further information on the application process.
Applications are initially viewed by all Staff. Since notifications should be discussed only with Modmins, it is essential that you do not mention any that you have. Applications mentioning notifications will be denied or sent to a Modmin board where they will not have the benefit of being assessed by existing Developers.
In the application, be sure to tell us why you feel your personality and characteristics make you a team player. Provide examples if possible.
If you have evidence of your qualifications, be sure to include links. For example, links to a website you made or contribute to, or links to threads on ACC that may help prove your qualifications.
Submit only one application in a six month period. If you've not had a response, you may reapply six months after your previous application or if we announce that Developer applications are required.
Wait for us to contact you. We will contact you only if your application is successful and if we are in need of additional Developers.