There were no logs The relevant test was commented out The developer responsible went on holiday The staging environment is shared We were notified of this issue by a customer A QA would've caught this Package update broke things in prod AWS services are different between environments "It's documented in Confluence" The documentation was out of date Time pressures (imagined or otherwise) Type checking would've caught this Unmerged PR to fix this The logs did not show an error Low code coverage blamed Requirements changed Feature branch deploys A third party service was faulty "That's on the backlog" [new tech] would fix this Seed data is lacking Deploys are slow Microservice communication issues "It's a feature, not a bug" There were no logs The relevant test was commented out The developer responsible went on holiday The staging environment is shared We were notified of this issue by a customer A QA would've caught this Package update broke things in prod AWS services are different between environments "It's documented in Confluence" The documentation was out of date Time pressures (imagined or otherwise) Type checking would've caught this Unmerged PR to fix this The logs did not show an error Low code coverage blamed Requirements changed Feature branch deploys A third party service was faulty "That's on the backlog" [new tech] would fix this Seed data is lacking Deploys are slow Microservice communication issues "It's a feature, not a bug"
(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.
There were no logs
The relevant test was commented out
The developer responsible went on holiday
The staging environment is shared
We were notified of this issue by a customer
A QA would've caught this
Package update broke things in prod
AWS services are different between environments
"It's documented in Confluence"
The documentation was out of date
Time pressures (imagined or otherwise)
Type checking would've caught this
Unmerged PR to fix this
The logs did not show an error
Low code coverage blamed
Requirements changed
Feature branch deploys
A third party service was faulty
"That's on the backlog"
[new tech] would fix this
Seed data is lacking
Deploys are slow
Microservice communication issues
"It's a feature, not a bug"