SoftwareversioningchangesSDC isblamed for amissingCAVAfeatureMultipleinstrumentteamscomplain to usabout MenloMenloasks forAWSaccountsSDC getsblamed formissing infowe asked forSDC isaskedto fly outto MenloWe get askeda questionthat should befor instrumentteamsFilenamingconventionchangesSomeoneimplies SDCwork isunimportantNo femalesoftwareengineersfrom MenloMenlocopies ourcode withoutcreditMenlobreaks reporules andnever fixesthemWe need toexplain howdockerworks toMenloMissinginputs is abig issue ifit's from theSDCSDC is stillmissing L1algorithmsby DecIMAPComms teamconflatesMenlo andLASPMenloactuallygets weeklymeetingsMenlotakes creditfor an SDCfeatureOne weeksprintcausesproblemsDependencychangespost-JanMore than 2people fromMenlo quitbefore JanSDC isasked todo someL3 workMaintenancequestion isn'tanswered byFebSomeoneexternalbreaksinfraSoftwareversioningchangesSDC isblamed for amissingCAVAfeatureMultipleinstrumentteamscomplain to usabout MenloMenloasks forAWSaccountsSDC getsblamed formissing infowe asked forSDC isaskedto fly outto MenloWe get askeda questionthat should befor instrumentteamsFilenamingconventionchangesSomeoneimplies SDCwork isunimportantNo femalesoftwareengineersfrom MenloMenlocopies ourcode withoutcreditMenlobreaks reporules andnever fixesthemWe need toexplain howdockerworks toMenloMissinginputs is abig issue ifit's from theSDCSDC is stillmissing L1algorithmsby DecIMAPComms teamconflatesMenlo andLASPMenloactuallygets weeklymeetingsMenlotakes creditfor an SDCfeatureOne weeksprintcausesproblemsDependencychangespost-JanMore than 2people fromMenlo quitbefore JanSDC isasked todo someL3 workMaintenancequestion isn'tanswered byFebSomeoneexternalbreaksinfra

IMAP SDC Bingo (Aug 2024) - Call List

(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.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. Software versioning changes
  2. SDC is blamed for a missing CAVA feature
  3. Multiple instrument teams complain to us about Menlo
  4. Menlo asks for AWS accounts
  5. SDC gets blamed for missing info we asked for
  6. SDC is asked to fly out to Menlo
  7. We get asked a question that should be for instrument teams
  8. File naming convention changes
  9. Someone implies SDC work is unimportant
  10. No female software engineers from Menlo
  11. Menlo copies our code without credit
  12. Menlo breaks repo rules and never fixes them
  13. We need to explain how docker works to Menlo
  14. Missing inputs is a big issue if it's from the SDC
  15. SDC is still missing L1 algorithms by Dec
  16. IMAP Comms team conflates Menlo and LASP
  17. Menlo actually gets weekly meetings
  18. Menlo takes credit for an SDC feature
  19. One week sprint causes problems
  20. Dependency changes post-Jan
  21. More than 2 people from Menlo quit before Jan
  22. SDC is asked to do some L3 work
  23. Maintenance question isn't answered by Feb
  24. Someone external breaks infra