Deploys are slow Unmerged PR to fix this Low code coverage blamed A third party service was faulty There were no logs "It's documented in Confluence" Seed data is lacking "That's on the backlog" Package update broke things in prod The relevant test was commented out Time pressures (imagined or otherwise) Requirements changed The developer responsible went on holiday "It's a feature, not a bug" The documentation was out of date Microservice communication issues The staging environment is shared A QA would've caught this We were notified of this issue by a customer [new tech] would fix this Feature branch deploys The logs did not show an error AWS services are different between environments Type checking would've caught this Deploys are slow Unmerged PR to fix this Low code coverage blamed A third party service was faulty There were no logs "It's documented in Confluence" Seed data is lacking "That's on the backlog" Package update broke things in prod The relevant test was commented out Time pressures (imagined or otherwise) Requirements changed The developer responsible went on holiday "It's a feature, not a bug" The documentation was out of date Microservice communication issues The staging environment is shared A QA would've caught this We were notified of this issue by a customer [new tech] would fix this Feature branch deploys The logs did not show an error AWS services are different between environments Type checking would've caught this
(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.
Deploys are slow
Unmerged PR to fix this
Low code coverage blamed
A third party service was faulty
There were no logs
"It's documented in Confluence"
Seed data is lacking
"That's on the backlog"
Package update broke things in prod
The relevant test was commented out
Time pressures (imagined or otherwise)
Requirements changed
The developer responsible went on holiday
"It's a feature, not a bug"
The documentation was out of date
Microservice communication issues
The staging environment is shared
A QA would've caught this
We were notified of this issue by a customer
[new tech] would fix this
Feature branch deploys
The logs did not show an error
AWS services are different between environments
Type checking would've caught this