/
23T3 Week 10

23T3 Week 10

 

Date & Time

Thursday 16 November 2023 3:00pm-5:00pm

Participants

Chloe, Jasmine, Sijin, Shaam, Ray, Sally, Brendan, Lucy, Jeremy, Ollie, Michael S, Michael V, Eklavya, Manhua, him

The Boys (Shaam, Eklavya, Michael)

  • Did stuff for the year, but not this week. Manhua was wrong.

  • Multiple timetables:

    • Learnt that he doesn’t like ‘likes’ FE

    • Eklavya: enjoyed the ticket, he was not too fond of history. “It was good

    • Probably not the best as an onboarding ticket, was too difficult. But still helped them learn about the code base, kinda like thrown into the deep end.

    • It was nice having a feature that they could own

Michael (as part of the boyz because he had a lot to say)

  • Liked working with Shaam and Eklavya, but then was put by himself.

  • Would have liked to still have partner to work with the later tickets

Jasmine

  • Shifted the timetable times

  • Implemented the clear timetable with Sally

  • Right click menu for the events, was a chunky one

  • Disabled the dragging of tutor cards

  • Side quest: guide on how to use Notangles, in the progress, made the step by step for it!

  • Liked the blue mountains trip and badminton event

Sijin

  • Gave us just jazz hands and lots of fun facts (poetry)

  • Felt more confident this year and got to see more the codebase

  • Understands types now

  • Liked that the meetings weren’t on the weekend

    • Initially was a bit hard for the online/hybrid people

  • Have less sporting bonding activities such as mini golf for more inclusivity!

  • Finally addressed by Jeremy as Sijin and not “the google one”

Sally

  • With the right click menu for the events, she learnt that she didn’t like CSS

  • Prefer working with others as well

 

General Feedback and Improvements for 2024!

  • Have more communication with Platforms and UIUX, so that work is not depending on them. We felt social timetabling was held back by this.

  • Felt that the work from last year was difficult to continue from.

    • Communicate with the previous team’s people (especially at beginning of the year) who worked on a particular feature that will be worked on this year.

 

 

Related content