In 2024, we have been given the liberty to focus (almost!) entirely on feature implementations! Some pivotal areas that need to be handled are:

• Increased data collection: an app like Unilectives becomes obsolete without many reviews.

  • A Reddit-scraping initiative was launched at the end of 2023, but this has yet to be completed;

  • MyExperience.

• Releasing new features such as:

  • Unilectives wrapped: a fun end-of-year feature that reviews interesting statistics like the most viewed course, etc

  • More course tags (e.g. wam booster, trending courses);

  • User profiles and statistics (e.g. highest upvotes, most number of reviews);

  • Dark mode;

  • Strengthening security;

  • Other ideas are completely open and welcome for discussion with the team.

The main way to achieve these is through proper time management, including clear deadlines as seen in the rest of the Confluence.

We want to improve the quality of course experience for the student body.

Openness, honesty, and constructive feedback.

Communication. We are all human and life happens; sometimes we are busier and sometimes we are more relaxed. But the important thing is to communicate and let others know where you are at so we can work as a team and meet in the middle.

You get what you give in. This is a great opportunity and what you have to gain (skills and fun experiences alike) is proportional to the commitment you give.

Unilectives wrapped

• Frontend: Design is done, we need to code it up

• Database queries

• Design which statistics to keep track of

Quality of life features

• More course tags (e.g. wam booster, trending courses)

• Updating course information to 2024

• Filtering courses

• Fixing truncated descriptions

Integration with myExperience --- WIP

• Start by myexperience@unsw.edu.au then gauge at what work needs to be done.

Open to suggestions!

A fun, welcoming environment where people are able to explore and nurture their ideas. We strive to strike a balance between a productive and efficient environment, and one that is memorably enjoyable---not something too serious and where people feel like they are coding for their lives.

• A 65-35 split between working and bonding

• Bonding: what ideas for fun outings do you want to do as a team? How often would you like them to be?

Base frequency of weekly meetings. This is open to discussion and accomodation given the context (e.g. exams, etc.)

• Stand-ups: What have you done? What is stopping you? What can you improve on? What are you going to do next?

• Part of 2 Week Sprints

• Each fortnight we’ll have a sprint review and planning

• We’ll try to meet in person but we’ll ask subcom’s opinions on it

Weekly meetings. It is not feasible to brute force commitment out of people, so our goal is to foster an environment that naturally instills eagerness. We will aim to do this through the balance between work and bondings, and communication in accomodating for others' schedules and ideas.

Fostering an enthusiastic and active environment. A big part of this is encouraging open communication, so that when people are beginning to have concerns and dissatisfactions (as is human), we are able to work through that.

At an individual level, personal check-ups will be sought when we feel is necessary. This will most likely be based on an overall gauge at a subcomittee’s activity and engagement. Then at a group level; weekly.