/
Term 3 week 4 backend Retro

Term 3 week 4 backend Retro

Owned by Peter Derias (Unlicensed), created
Last updated: Oct 27, 2022
2 min read

​ Overview

Reflect on past work and identify opportunities for improvement by following the instructions for the Retrospective Play.

Date

​Oct 4, 2022

Team

​Circles BE

Participants

​@Peter Derias (Unlicensed) @Hussain Nawaz (Unlicensed) @Elliot Rotenstein (Unlicensed) @Thomas Zhao (Unlicensed) @Mae Vuong (Unlicensed) @Nyah Inglis (Unlicensed)

Apologies

@Sona Reddy (Unlicensed) @Josh Harcombe (Unlicensed)

What happened last time?

  • backend migration: cleaning up rough edges

  • Retro meta discussion

  • discussed reviews going back and forth too much

  • Low hanging fruit issue - easy stuff is gone is this a problem?

 Retrospective

Add your Start doing, Stop doing, and Keep doing items to the table below. We'll use these to talk about how we can improve our process going forward.

You should try to contribute at least 1 suggestion to each column! Don’t be afraid to be critical. We are here to improve!

Think about the “Circles meta”. Our processes, our hopes, and so on.

Start doing - what are we missing?

Stop doing - what went wrong?

Kudos - warm and fuzzies

Keep doing - what went well?

Start doing - what are we missing?

Stop doing - what went wrong?

Kudos - warm and fuzzies

Keep doing - what went well?

  • ​set a timeout on blocking ticket?

  • backend migration ad-hoc changes @Peter Derias (Unlicensed) stop changing the validation, youre breaking other people’s code!

  • → branch protection for that branch?

  • rename that branch, for real!!!!

  • @Nyah Inglis (Unlicensed) for suffering through setup lol

  • The new ppl are starting to get the hang of stuff

  • socials (notangles envy)

 

  • Peter thanks for helping me lol I woulda been lost

  • found a new standup time that works for everyone

  • ^^ would love to meet everybody

  • why is Technical merging branches / PRs

  • thanks @Hussain Nawaz (Unlicensed) for grinding out maturity requirements Really cool design

 

  • ^^^ hybrid meetings?

  • Still, only a small subset of us are reviewing PRs

  • Auto-planning is really epic 🧠 kudo to Peter

 

  • peter promised us food

  • If going to not get started on a ticket all week, pls don’t self-assign; but idk <= set a timeout on blocking ticket?

  • Blazingly fast PR reviews

 

  • fr tho, need to meet the new ppl

  • Maybe should go in Start Doing but, :Crazyidea:, the mixing of looping, next, wierd index recursion in create.py is a bit

  • Nesting to a tree during as a post-process action in tokenising would lead to very clean parser

 

 

  • team hyperkarting session

  • Not actually sure where we are on the migration

 

 

  • ^^ yes I am stupid for missing this, will set up a BE only event

 

 

 

​ Action items

​

​Find the plugin that adds how long something has been in a column
branch protection for be migration
set up the tuesday thingo
1 pr per person - rng someone to be forced to do PR
Talk about BE migration
Make next year refactor create.py

​ Confidence in timeline

Based on what we have talked about, are there any changes we should make to our delivery plans?

⏲️Proposed Timeline