SDC isblamed for amissingCAVAfeatureWe get askeda questionthat should befor instrumentteamsMenloasks forAWSaccountsDependencychangespost-JanSDC is stillmissing L1algorithmsby DecSoftwareversioningchangesSDC isasked todo someL3 workSomeoneimplies SDCwork isunimportantWe need toexplain howdockerworks toMenloNo femalesoftwareengineersfrom MenloMenlocopies ourcode withoutcreditFilenamingconventionchangesMaintenancequestion isn'tanswered byFebMenlotakes creditfor an SDCfeatureOne weeksprintcausesproblemsSDC isaskedto fly outto MenloMenloactuallygets weeklymeetingsIMAPComms teamconflatesMenlo andLASPSomeoneexternalbreaksinfraMore than 2people fromMenlo quitbefore JanMultipleinstrumentteamscomplain to usabout MenloMenlobreaks reporules andnever fixesthemSDC getsblamed formissing infowe asked forMissinginputs is abig issue ifit's from theSDCSDC isblamed for amissingCAVAfeatureWe get askeda questionthat should befor instrumentteamsMenloasks forAWSaccountsDependencychangespost-JanSDC is stillmissing L1algorithmsby DecSoftwareversioningchangesSDC isasked todo someL3 workSomeoneimplies SDCwork isunimportantWe need toexplain howdockerworks toMenloNo femalesoftwareengineersfrom MenloMenlocopies ourcode withoutcreditFilenamingconventionchangesMaintenancequestion isn'tanswered byFebMenlotakes creditfor an SDCfeatureOne weeksprintcausesproblemsSDC isaskedto fly outto MenloMenloactuallygets weeklymeetingsIMAPComms teamconflatesMenlo andLASPSomeoneexternalbreaksinfraMore than 2people fromMenlo quitbefore JanMultipleinstrumentteamscomplain to usabout MenloMenlobreaks reporules andnever fixesthemSDC getsblamed formissing infowe asked forMissinginputs is abig issue ifit's from theSDC

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