Menloasks forAWSaccountsFilenamingconventionchangesNo femalesoftwareengineersfrom MenloSDC isblamed for amissingCAVAfeatureSoftwareversioningchangesOne weeksprintcausesproblemsMenlotakes creditfor an SDCfeatureMenloactuallygets weeklymeetingsMenlobreaks reporules andnever fixesthemSDC is stillmissing L1algorithmsby DecSDC getsblamed formissing infowe asked forMenlocopies ourcode withoutcreditMaintenancequestion isn'tanswered byFebMore than 2people fromMenlo quitbefore JanSDC isaskedto fly outto MenloWe need toexplain howdockerworks toMenloSomeoneimplies SDCwork isunimportantDependencychangespost-JanMultipleinstrumentteamscomplain to usabout MenloIMAPComms teamconflatesMenlo andLASPSDC isasked todo someL3 workSomeoneexternalbreaksinfraMissinginputs is abig issue ifit's from theSDCWe get askeda questionthat should befor instrumentteamsMenloasks forAWSaccountsFilenamingconventionchangesNo femalesoftwareengineersfrom MenloSDC isblamed for amissingCAVAfeatureSoftwareversioningchangesOne weeksprintcausesproblemsMenlotakes creditfor an SDCfeatureMenloactuallygets weeklymeetingsMenlobreaks reporules andnever fixesthemSDC is stillmissing L1algorithmsby DecSDC getsblamed formissing infowe asked forMenlocopies ourcode withoutcreditMaintenancequestion isn'tanswered byFebMore than 2people fromMenlo quitbefore JanSDC isaskedto fly outto MenloWe need toexplain howdockerworks toMenloSomeoneimplies SDCwork isunimportantDependencychangespost-JanMultipleinstrumentteamscomplain to usabout MenloIMAPComms teamconflatesMenlo andLASPSDC isasked todo someL3 workSomeoneexternalbreaksinfraMissinginputs is abig issue ifit's from theSDCWe get askeda questionthat should befor instrumentteams

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