Menloactuallygets weeklymeetingsWe get askeda questionthat should befor instrumentteamsWe need toexplain howdockerworks toMenloNo femalesoftwareengineersfrom MenloSomeoneexternalbreaksinfraSDC isasked todo someL3 workDependencychangespost-JanSoftwareversioningchangesSDC is stillmissing L1algorithmsby DecFilenamingconventionchangesSDC isaskedto fly outto MenloMultipleinstrumentteamscomplain to usabout MenloSDC isblamed for amissingCAVAfeatureMenlocopies ourcode withoutcreditMore than 2people fromMenlo quitbefore JanMenlobreaks reporules andnever fixesthemMenlotakes creditfor an SDCfeatureSomeoneimplies SDCwork isunimportantSDC getsblamed formissing infowe asked forMenloasks forAWSaccountsOne weeksprintcausesproblemsMissinginputs is abig issue ifit's from theSDCIMAPComms teamconflatesMenlo andLASPMaintenancequestion isn'tanswered byFebMenloactuallygets weeklymeetingsWe get askeda questionthat should befor instrumentteamsWe need toexplain howdockerworks toMenloNo femalesoftwareengineersfrom MenloSomeoneexternalbreaksinfraSDC isasked todo someL3 workDependencychangespost-JanSoftwareversioningchangesSDC is stillmissing L1algorithmsby DecFilenamingconventionchangesSDC isaskedto fly outto MenloMultipleinstrumentteamscomplain to usabout MenloSDC isblamed for amissingCAVAfeatureMenlocopies ourcode withoutcreditMore than 2people fromMenlo quitbefore JanMenlobreaks reporules andnever fixesthemMenlotakes creditfor an SDCfeatureSomeoneimplies SDCwork isunimportantSDC getsblamed formissing infowe asked forMenloasks forAWSaccountsOne weeksprintcausesproblemsMissinginputs is abig issue ifit's from theSDCIMAPComms teamconflatesMenlo andLASPMaintenancequestion isn'tanswered byFeb

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