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