SoftwareversioningchangesMissinginputs is abig issue ifit's from theSDCDependencychangespost-JanSDC isasked todo someL3 workMenlocopies ourcode withoutcreditMultipleinstrumentteamscomplain to usabout MenloMenlotakes creditfor an SDCfeatureMaintenancequestion isn'tanswered byFebSDC getsblamed formissing infowe asked forSDC isblamed for amissingCAVAfeatureNo femalesoftwareengineersfrom MenloIMAPComms teamconflatesMenlo andLASPSDC is stillmissing L1algorithmsby DecSomeoneimplies SDCwork isunimportantWe get askeda questionthat should befor instrumentteamsFilenamingconventionchangesMenloactuallygets weeklymeetingsOne weeksprintcausesproblemsMenlobreaks reporules andnever fixesthemMenloasks forAWSaccountsWe need toexplain howdockerworks toMenloSomeoneexternalbreaksinfraSDC isaskedto fly outto MenloMore than 2people fromMenlo quitbefore JanSoftwareversioningchangesMissinginputs is abig issue ifit's from theSDCDependencychangespost-JanSDC isasked todo someL3 workMenlocopies ourcode withoutcreditMultipleinstrumentteamscomplain to usabout MenloMenlotakes creditfor an SDCfeatureMaintenancequestion isn'tanswered byFebSDC getsblamed formissing infowe asked forSDC isblamed for amissingCAVAfeatureNo femalesoftwareengineersfrom MenloIMAPComms teamconflatesMenlo andLASPSDC is stillmissing L1algorithmsby DecSomeoneimplies SDCwork isunimportantWe get askeda questionthat should befor instrumentteamsFilenamingconventionchangesMenloactuallygets weeklymeetingsOne weeksprintcausesproblemsMenlobreaks reporules andnever fixesthemMenloasks forAWSaccountsWe need toexplain howdockerworks toMenloSomeoneexternalbreaksinfraSDC isaskedto fly outto MenloMore than 2people fromMenlo quitbefore Jan

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