Visions

Primary Vision: Empower all CSE students professionally, socially, technically and personally.

The overarching purpose of CSESoc Development has remained the same each year, but for good reason. We are a community of students for students, and we want to give all members of CSESoc Development opportunities and a positive experience in these key areas.

Provide opportunities for students to upskill themselves and explore things not taught in courses.

This looks like:

• Giving students opportunities to learn more about teamwork and programming through our flagship projects

• Guide beginner-level students in building their own web applications through the training program

• Providing other avenues for students to pick up skills, such as in design and content creation

• Creating ways for students to work on projects they want

Creating education content and events that the CSE community has shown interest in.

This looks like:

• Ensure that this content is approachable and digestible by new comers to the area

• Ensuring events/content are easily accessible for students

• Guiding students through the overwhelming information about computer science available to them online

• Supporting students to create their own self-learning path through their computer science career

• Teach content not easily accessible online or not well covered by the UNSW curriculum

• Supplementing existing UNSW courses for a better student experience in their Comp Sci degree

Cultivating a supportive, inclusive, fun and learning-driven student developer culture.

This looks like:

• Giving lots of opportunities for students to learn and upskill themselves (see visions above)

• Be approachable and welcoming - lower the barrier to participation as much as possible

• Reducing impostor syndrome so everyone can feel comfortable in asking questions and participating

• Implementing the Culture subcommittee to ensure everyone is supported and included, as well as to prevent burnouts and mental stress

Be approachable and welcoming - lower the barrier to participation as much as possible.

This looks like:

• Having a rolling recruitment system, so more people can have the opportunity to partake in the development portfolio and the positive experience we try to cultivate

• Promoting our projects through content that showcases our projects and the people working on them

• Ensure that the only benchmark being monitored is progress, whether it be through learning or production (striving for a balance between this and meeting deadlines)

Be transparent - anything we can make open to the public, should be made open to the public.

This looks like:

• Making all documents and communications as public as possible, use private channels/permissions as little as possible

• Communicating our expectations - we want to encourage progress and upskilling through working on projects, but remind people that development is supposed to be fun and voluntary

Seek feedback and self-reflect on everything we do, whether its our events, our content, or our internal processes.

This looks like:

• Continually participate with the CSE community, through a variety of mediums such as forms, events and Discord servers, and actively receive feedback

• Hold debriefs after events to go over what went well and what could be improved

• Hold regular meetings with the executives, directors and subcommittee members to make sure everyone’s opinions and ideas are heard, and to allow them to be more involved in executive decisions

• Communicating more effectively with the School of CSE, including academics and other staff

Provide a variety of useful apps, for the benefit of Development and CSE more broadly.

This looks like:

• Combining the styles of all CSESoc projects such that the community gets a unified experience

• Integrating existing projects with each other, to make user experience smoother and to reduce technical debt

Goals

Projects

• Project-specific: status:PROVIDE OPPORTUNITIES FOR STUDENTS

  • Get Chaos into a fully-functional and reliable product for future recruitments of CSESoc and other societies

  • Expand Circles to have more additional features, to overall enhance the degree-planning experience

  • Finish the expansion of CSElectives into Uni-lectives

  • Have Discord Bot fulfill the needs of both CSESoc and the CSE community at large

  • Release the new version of the Freerooms' frontend and make the app into a fully-functional product

  • Release and promote the use of Jobsboard to the general public, both sponsors and students

  • Maintain Notangles

  • Expand Structs.sh to provide visualisations for more data structures and algorithms

  • Expand Website’s OT concurrent editor to support more complex objects and possibly expand to event creation

• Create a unified design system for all CSESoc flagship projects status:BE APPROACHABLE AND WELCOMING

• Consolidate the uni-planning projects (i.e. Circles, CSElectives, Freerooms and Notangles) into one unified web application status:PROVIDE USEFUL APPS

• Increase usage of all projects by 50% status:BE APPROACHABLE AND WELCOMING

Culture

• Have at least one road trip in the year, preferably in T1/T2 holidays for people to bond and get comfortable with each other status:Cultivating a supportive, inclusive, fun and learning-driven student developer culture

• Have at least one Development-wide event per term status:Cultivating a supportive, inclusive, fun and learning-driven student developer culture

• Do a mid-term check up on all teams status:Cultivating a supportive, inclusive, fun and learning-driven student developer culture

•  

Content

• Create and release at least one large-scale initiative per term status:BE APPROACHABLE AND WELCOMING

• Release more articles to increase the exposure of our initiatives and the members that work on them status:BE APPROACHABLE AND WELCOMING

•  

UI/UX

• Create a unified design system for all CSESoc flagship projects status:BE APPROACHABLE AND WELCOMING

• Revamp the designs of all the CSESoc flagship projects

Technical

• Acquire AWS partnership and move all existing architecture to external server

• Create a federated authentication system

• Create a proper analytics and tracing platform to view statistics across all products

Be transparent - anything we can make open to the public, should be made open to the public.

Education

• Initiatives status:Creating education content and events that the CSE community has shown interest in.

  • week 1-5 opendev ?? t2-3?

  • 1 industry workshop every 3 weeks?

  • one article by each subcom

  • discussion forum for interesting technolgies/projects

  • 1 tik tok/instagram reel a week

  • create training program

• Quality status:Creating education content and events that the CSE community has shown interest in.

  • dryruns on workshops

  • acquire feedback for all events and implement the feedback that is relevant status:Seek feedback and self-reflect on everything we do, whether its our events, our content, or our internal processes.

  • 1 survey/wide audience communication per week with cohort about what topics they're interested in (can be done at bbqs or give survey)

• Vibe status:Cultivating a supportive, inclusive, fun and learning-driven student developer culture.

  • Have every edu member in a discord and each member has felt comfortable sending at least 3 msgs

  • allow internals to make friendships they can outlast past the end of the society

  • keep in contact with any one interested in teaching/edu

  • 1 outing per 2 weeks for subcom?