Menlocopies ourcode withoutcreditMenloactuallygets weeklymeetingsSDC getsblamed formissing infowe asked forNo femalesoftwareengineersfrom MenloSDC isasked todo someL3 workMenlobreaks reporules andnever fixesthemSDC is stillmissing L1algorithmsby DecSDC isblamed for amissingCAVAfeatureWe get askeda questionthat should befor instrumentteamsMissinginputs is abig issue ifit's from theSDCMenlotakes creditfor an SDCfeatureSoftwareversioningchangesMultipleinstrumentteamscomplain to usabout MenloMore than 2people fromMenlo quitbefore JanFilenamingconventionchangesOne weeksprintcausesproblemsMaintenancequestion isn'tanswered byFebSomeoneexternalbreaksinfraWe need toexplain howdockerworks toMenloSomeoneimplies SDCwork isunimportantIMAPComms teamconflatesMenlo andLASPMenloasks forAWSaccountsDependencychangespost-JanSDC isaskedto fly outto MenloMenlocopies ourcode withoutcreditMenloactuallygets weeklymeetingsSDC getsblamed formissing infowe asked forNo femalesoftwareengineersfrom MenloSDC isasked todo someL3 workMenlobreaks reporules andnever fixesthemSDC is stillmissing L1algorithmsby DecSDC isblamed for amissingCAVAfeatureWe get askeda questionthat should befor instrumentteamsMissinginputs is abig issue ifit's from theSDCMenlotakes creditfor an SDCfeatureSoftwareversioningchangesMultipleinstrumentteamscomplain to usabout MenloMore than 2people fromMenlo quitbefore JanFilenamingconventionchangesOne weeksprintcausesproblemsMaintenancequestion isn'tanswered byFebSomeoneexternalbreaksinfraWe need toexplain howdockerworks toMenloSomeoneimplies SDCwork isunimportantIMAPComms teamconflatesMenlo andLASPMenloasks forAWSaccountsDependencychangespost-JanSDC isaskedto fly outto 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. Menlo copies our code without credit
  2. Menlo actually gets weekly meetings
  3. SDC gets blamed for missing info we asked for
  4. No female software engineers from Menlo
  5. SDC is asked to do some L3 work
  6. Menlo breaks repo rules and never fixes them
  7. SDC is still missing L1 algorithms by Dec
  8. SDC is blamed for a missing CAVA feature
  9. We get asked a question that should be for instrument teams
  10. Missing inputs is a big issue if it's from the SDC
  11. Menlo takes credit for an SDC feature
  12. Software versioning changes
  13. Multiple instrument teams complain to us about Menlo
  14. More than 2 people from Menlo quit before Jan
  15. File naming convention changes
  16. One week sprint causes problems
  17. Maintenance question isn't answered by Feb
  18. Someone external breaks infra
  19. We need to explain how docker works to Menlo
  20. Someone implies SDC work is unimportant
  21. IMAP Comms team conflates Menlo and LASP
  22. Menlo asks for AWS accounts
  23. Dependency changes post-Jan
  24. SDC is asked to fly out to Menlo