Page MenuHomePhabricator

Retrospective and learnings from the Parser/Cite clone incident
Closed, ResolvedPublic3 Estimated Story Points

Description

Event Timeline

awight set the point value for this task to 8.Dec 19 2019, 10:40 AM

Adding a random story point estimate. The incident report looks complete, I'll tick that box.

@thiemowmde @awight To the remaining open steps above:

Do we want to schedule that meeting? Who should be in it?

  • Document learnings.

We can probably generate insights during that meeting.

I would still love to have a round of people (whoever is interested) sit together and brag about how broken PHP is. ;-) No, seriously, I think a 30 minutes brainstorming session would be really helpful. Personally, I prefer to have both @awight as well as @WMDE-Fisch in there. @WMDE-Fisch, I feel it's best if you suggest a time.

I scheduled a little retro session for next Monday.

WMDE-Fisch changed the point value for this task from 8 to 3.Jan 8 2020, 12:50 PM
WMDE-Fisch moved this task from Sprint Backlog to Doing on the WMDE-QWERTY-Sprint-2020-01-08 board.
thiemowmde closed this task as Resolved.EditedJan 23 2020, 10:10 AM
thiemowmde claimed this task.

Results from said meeting: https://docs.google.com/document/d/1m01PqK5o18FyRkHAixtJBOQ3qhJDpY8f10NOBggcUE4

Brief summary:

  • We used LogicException to lightly.
  • Should have been a type of error that resolves better for the user.
  • Should have been logged.
  • We will have a closer look into logs that are relevant for our products/features.
  • Team members will subscribe to relevant Phabricator tags to get notified earlier.