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