Multipleinstrumentteamscomplain to usabout MenloSoftwareversioningchangesDependencychangespost-JanIMAPComms teamconflatesMenlo andLASPSDC is stillmissing L1algorithmsby DecNo femalesoftwareengineersfrom MenloOne weeksprintcausesproblemsSomeoneexternalbreaksinfraMenlotakes creditfor an SDCfeatureSDC getsblamed formissing infowe asked forWe get askeda questionthat should befor instrumentteamsFilenamingconventionchangesSDC isblamed for amissingCAVAfeatureWe need toexplain howdockerworks toMenloSDC isaskedto fly outto MenloMenloactuallygets weeklymeetingsMissinginputs is abig issue ifit's from theSDCMenlobreaks reporules andnever fixesthemMenloasks forAWSaccountsMaintenancequestion isn'tanswered byFebSomeoneimplies SDCwork isunimportantMore than 2people fromMenlo quitbefore JanSDC isasked todo someL3 workMenlocopies ourcode withoutcreditMultipleinstrumentteamscomplain to usabout MenloSoftwareversioningchangesDependencychangespost-JanIMAPComms teamconflatesMenlo andLASPSDC is stillmissing L1algorithmsby DecNo femalesoftwareengineersfrom MenloOne weeksprintcausesproblemsSomeoneexternalbreaksinfraMenlotakes creditfor an SDCfeatureSDC getsblamed formissing infowe asked forWe get askeda questionthat should befor instrumentteamsFilenamingconventionchangesSDC isblamed for amissingCAVAfeatureWe need toexplain howdockerworks toMenloSDC isaskedto fly outto MenloMenloactuallygets weeklymeetingsMissinginputs is abig issue ifit's from theSDCMenlobreaks reporules andnever fixesthemMenloasks forAWSaccountsMaintenancequestion isn'tanswered byFebSomeoneimplies SDCwork isunimportantMore than 2people fromMenlo quitbefore JanSDC isasked todo someL3 workMenlocopies ourcode withoutcredit

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