SDC isaskedto fly outto MenloMenloasks forAWSaccountsMenlotakes creditfor an SDCfeatureMenlobreaks reporules andnever fixesthemMaintenancequestion isn'tanswered byFebSDC isblamed for amissingCAVAfeatureSomeoneexternalbreaksinfraWe get askeda questionthat should befor instrumentteamsDependencychangespost-JanSDC is stillmissing L1algorithmsby DecSDC isasked todo someL3 workSDC getsblamed formissing infowe asked forSoftwareversioningchangesMissinginputs is abig issue ifit's from theSDCMenloactuallygets weeklymeetingsIMAPComms teamconflatesMenlo andLASPSomeoneimplies SDCwork isunimportantMore than 2people fromMenlo quitbefore JanOne weeksprintcausesproblemsMultipleinstrumentteamscomplain to usabout MenloFilenamingconventionchangesWe need toexplain howdockerworks toMenloNo femalesoftwareengineersfrom MenloMenlocopies ourcode withoutcreditSDC isaskedto fly outto MenloMenloasks forAWSaccountsMenlotakes creditfor an SDCfeatureMenlobreaks reporules andnever fixesthemMaintenancequestion isn'tanswered byFebSDC isblamed for amissingCAVAfeatureSomeoneexternalbreaksinfraWe get askeda questionthat should befor instrumentteamsDependencychangespost-JanSDC is stillmissing L1algorithmsby DecSDC isasked todo someL3 workSDC getsblamed formissing infowe asked forSoftwareversioningchangesMissinginputs is abig issue ifit's from theSDCMenloactuallygets weeklymeetingsIMAPComms teamconflatesMenlo andLASPSomeoneimplies SDCwork isunimportantMore than 2people fromMenlo quitbefore JanOne weeksprintcausesproblemsMultipleinstrumentteamscomplain to usabout MenloFilenamingconventionchangesWe need toexplain howdockerworks toMenloNo femalesoftwareengineersfrom MenloMenlocopies 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. SDC is asked to fly out to Menlo
  2. Menlo asks for AWS accounts
  3. Menlo takes credit for an SDC feature
  4. Menlo breaks repo rules and never fixes them
  5. Maintenance question isn't answered by Feb
  6. SDC is blamed for a missing CAVA feature
  7. Someone external breaks infra
  8. We get asked a question that should be for instrument teams
  9. Dependency changes post-Jan
  10. SDC is still missing L1 algorithms by Dec
  11. SDC is asked to do some L3 work
  12. SDC gets blamed for missing info we asked for
  13. Software versioning changes
  14. Missing inputs is a big issue if it's from the SDC
  15. Menlo actually gets weekly meetings
  16. IMAP Comms team conflates Menlo and LASP
  17. Someone implies SDC work is unimportant
  18. More than 2 people from Menlo quit before Jan
  19. One week sprint causes problems
  20. Multiple instrument teams complain to us about Menlo
  21. File naming convention changes
  22. We need to explain how docker works to Menlo
  23. No female software engineers from Menlo
  24. Menlo copies our code without credit