Multipleinstrumentteamscomplain to usabout MenloOne weeksprintcausesproblemsDependencychangespost-JanMaintenancequestion isn'tanswered byFebMenlobreaks reporules andnever fixesthemSomeoneexternalbreaksinfraWe need toexplain howdockerworks toMenloFilenamingconventionchangesMissinginputs is abig issue ifit's from theSDCMenloactuallygets weeklymeetingsSDC isasked todo someL3 workSDC getsblamed formissing infowe asked forIMAPComms teamconflatesMenlo andLASPMenlocopies ourcode withoutcreditSoftwareversioningchangesSomeoneimplies SDCwork isunimportantSDC isblamed for amissingCAVAfeatureMenlotakes creditfor an SDCfeatureMore than 2people fromMenlo quitbefore JanMenloasks forAWSaccountsNo femalesoftwareengineersfrom MenloSDC isaskedto fly outto MenloSDC is stillmissing L1algorithmsby DecWe get askeda questionthat should befor instrumentteamsMultipleinstrumentteamscomplain to usabout MenloOne weeksprintcausesproblemsDependencychangespost-JanMaintenancequestion isn'tanswered byFebMenlobreaks reporules andnever fixesthemSomeoneexternalbreaksinfraWe need toexplain howdockerworks toMenloFilenamingconventionchangesMissinginputs is abig issue ifit's from theSDCMenloactuallygets weeklymeetingsSDC isasked todo someL3 workSDC getsblamed formissing infowe asked forIMAPComms teamconflatesMenlo andLASPMenlocopies ourcode withoutcreditSoftwareversioningchangesSomeoneimplies SDCwork isunimportantSDC isblamed for amissingCAVAfeatureMenlotakes creditfor an SDCfeatureMore than 2people fromMenlo quitbefore JanMenloasks forAWSaccountsNo femalesoftwareengineersfrom MenloSDC isaskedto fly outto MenloSDC is stillmissing L1algorithmsby DecWe get askeda questionthat should befor instrumentteams

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