Skip to content

Instantly share code, notes, and snippets.

@gregblake
Created February 12, 2020 14:29
Show Gist options
  • Select an option

  • Save gregblake/409e07cd89f8497a2e20f45d8a703750 to your computer and use it in GitHub Desktop.

Select an option

Save gregblake/409e07cd89f8497a2e20f45d8a703750 to your computer and use it in GitHub Desktop.
Standup Update -- Wednesday 2/12/2020

What did I do yesterday to help the team meet the sprint goal?

  • Completed the story that adds a new composite index to the connect_rooms table. This is in production. No new errors in Sentry.
  • Began working on two new stories:
    1. Add two new feature toggles for Connect search.
    2. Add a new permission for Connect search.
    • Both of these PR's received code review and testing approval. I merged both PR's in the afternoon. Another team reverted a PR shortly after that, so they shipped via emergency deployment. But I followed that deployment into production. No new errors in Sentry.
  • Worked on the story to optimize the connect_room_users query. A PR is open, and the feature is nearly completed.
  • Code review.
  • Chatted with Jenny about upgrading the mobile app from RN v0.59 to v0.60/v0.61.
  • Attended the All Hands meeting.

What will I do today to help the team meet the sprint goal?

  • Work on the story to optimize the connect_room_users query.
  • If the badge count PR receives testing approval, I'll be shipping that (otherwise I'll make any changes that are deemed necessary).
  • Monitor production changes after shipping the new index on connect_rooms (to determine if it's now faster, slower, or no change).
  • Pick up one of the next stories in the backlog (probably the ElasticSearch spike, but possibly the RN search UI story, or the story to setup search permissions on the web client).

Do I see any impediments that prevent me or the team from meeting the sprint goal?

  • No blockers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment