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