SDC isblamed for amissingCAVAfeatureMenloasks forAWSaccountsMaintenancequestion isn'tanswered byFebSDC getsblamed formissing infowe asked forMore than 2people fromMenlo quitbefore JanDependencychangespost-JanFilenamingconventionchangesMissinginputs is abig issue ifit's from theSDCSomeoneimplies SDCwork isunimportantMenlobreaks reporules andnever fixesthemMenlotakes creditfor an SDCfeatureNo femalesoftwareengineersfrom MenloSDC isaskedto fly outto MenloSoftwareversioningchangesSDC is stillmissing L1algorithmsby DecIMAPComms teamconflatesMenlo andLASPWe get askeda questionthat should befor instrumentteamsOne weeksprintcausesproblemsMenlocopies ourcode withoutcreditSomeoneexternalbreaksinfraWe need toexplain howdockerworks toMenloMenloactuallygets weeklymeetingsSDC isasked todo someL3 workMultipleinstrumentteamscomplain to usabout MenloSDC isblamed for amissingCAVAfeatureMenloasks forAWSaccountsMaintenancequestion isn'tanswered byFebSDC getsblamed formissing infowe asked forMore than 2people fromMenlo quitbefore JanDependencychangespost-JanFilenamingconventionchangesMissinginputs is abig issue ifit's from theSDCSomeoneimplies SDCwork isunimportantMenlobreaks reporules andnever fixesthemMenlotakes creditfor an SDCfeatureNo femalesoftwareengineersfrom MenloSDC isaskedto fly outto MenloSoftwareversioningchangesSDC is stillmissing L1algorithmsby DecIMAPComms teamconflatesMenlo andLASPWe get askeda questionthat should befor instrumentteamsOne weeksprintcausesproblemsMenlocopies ourcode withoutcreditSomeoneexternalbreaksinfraWe need toexplain howdockerworks toMenloMenloactuallygets weeklymeetingsSDC isasked todo someL3 workMultipleinstrumentteamscomplain to usabout Menlo

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