More than 2people fromMenlo quitbefore JanFilenamingconventionchangesSoftwareversioningchangesNo femalesoftwareengineersfrom MenloSDC isblamed for amissingCAVAfeatureIMAPComms teamconflatesMenlo andLASPSDC is stillmissing L1algorithmsby DecSDC isaskedto fly outto MenloOne weeksprintcausesproblemsMenloactuallygets weeklymeetingsMenlotakes creditfor an SDCfeatureWe need toexplain howdockerworks toMenloDependencychangespost-JanSDC getsblamed formissing infowe asked forMissinginputs is abig issue ifit's from theSDCMaintenancequestion isn'tanswered byFebSomeoneexternalbreaksinfraSomeoneimplies SDCwork isunimportantMultipleinstrumentteamscomplain to usabout MenloMenloasks forAWSaccountsMenlocopies ourcode withoutcreditMenlobreaks reporules andnever fixesthemWe get askeda questionthat should befor instrumentteamsSDC isasked todo someL3 workMore than 2people fromMenlo quitbefore JanFilenamingconventionchangesSoftwareversioningchangesNo femalesoftwareengineersfrom MenloSDC isblamed for amissingCAVAfeatureIMAPComms teamconflatesMenlo andLASPSDC is stillmissing L1algorithmsby DecSDC isaskedto fly outto MenloOne weeksprintcausesproblemsMenloactuallygets weeklymeetingsMenlotakes creditfor an SDCfeatureWe need toexplain howdockerworks toMenloDependencychangespost-JanSDC getsblamed formissing infowe asked forMissinginputs is abig issue ifit's from theSDCMaintenancequestion isn'tanswered byFebSomeoneexternalbreaksinfraSomeoneimplies SDCwork isunimportantMultipleinstrumentteamscomplain to usabout MenloMenloasks forAWSaccountsMenlocopies ourcode withoutcreditMenlobreaks reporules andnever fixesthemWe get askeda questionthat should befor instrumentteamsSDC isasked todo someL3 work

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