| |
---|
|
For the new leads | Given the large codebase, we found that letting a pair “own” a particular feature helped smooth out the development process since they would be most familiar with it and thus know how ti fix or extend it. Read every line of code in pull requests. Never allow sloppy code to be pushed to dev, as messiness compounds and will be difficult to fix in the future.
|
What was completed? | Major refactor at the start of the year (context api etc.) Autotimetabling Save timetable as ICS Expanded view to see more detail about a class/event Custom event creation and tutor support to make it easier to add the classes you are teaching More intuitive display of clashing classes Hotkeys (ctrl+z to undo, ctrl+y to redo and etc. for macOS) Local timezone conversion Automated updating of current year and term based on scraped data Automated scraping New backend for social timetabling (MVP ready) Sentry integration to catch bugs in prod Detailed documentation not only for overall concepts e.g. autotimetabling but also individual functions
|
What we did well? | Many in-person meetings and social events which fostered team bonding (thanks @Angella Pham (Unlicensed) I guess ) Many features were pushed out Pace of development was mostly consistent throughout the year Most people were motivated to work on the project
|
What can we implement next year? | |
What could be improved for next year? | “Next year won’t have me in it” - Angella Pham, Vice President (Development) 2023 “It was pretty dogshit actually” - Angella Pham, Vice President (Development) 2023 “More supportive leads would be nice” - Angella Pham, Vice President (Development) 2023 “Meeting locations were hard to find in the beginning” - Manhua
|
What would next year’s team look like given that there’ll be less major features? | |