Dependencychangespost-JanWe need toexplain howdockerworks toMenloMenlobreaks reporules andnever fixesthemMenloactuallygets weeklymeetingsMenlotakes creditfor an SDCfeatureSDC is stillmissing L1algorithmsby DecSDC getsblamed formissing infowe asked forIMAPComms teamconflatesMenlo andLASPMaintenancequestion isn'tanswered byFebWe get askeda questionthat should befor instrumentteamsSoftwareversioningchangesSDC isblamed for amissingCAVAfeatureMenloasks forAWSaccountsOne weeksprintcausesproblemsMenlocopies ourcode withoutcreditFilenamingconventionchangesMore than 2people fromMenlo quitbefore JanNo femalesoftwareengineersfrom MenloSomeoneimplies SDCwork isunimportantMissinginputs is abig issue ifit's from theSDCSomeoneexternalbreaksinfraSDC isasked todo someL3 workSDC isaskedto fly outto MenloMultipleinstrumentteamscomplain to usabout MenloDependencychangespost-JanWe need toexplain howdockerworks toMenloMenlobreaks reporules andnever fixesthemMenloactuallygets weeklymeetingsMenlotakes creditfor an SDCfeatureSDC is stillmissing L1algorithmsby DecSDC getsblamed formissing infowe asked forIMAPComms teamconflatesMenlo andLASPMaintenancequestion isn'tanswered byFebWe get askeda questionthat should befor instrumentteamsSoftwareversioningchangesSDC isblamed for amissingCAVAfeatureMenloasks forAWSaccountsOne weeksprintcausesproblemsMenlocopies ourcode withoutcreditFilenamingconventionchangesMore than 2people fromMenlo quitbefore JanNo femalesoftwareengineersfrom MenloSomeoneimplies SDCwork isunimportantMissinginputs is abig issue ifit's from theSDCSomeoneexternalbreaksinfraSDC isasked todo someL3 workSDC isaskedto fly outto MenloMultipleinstrumentteamscomplain to usabout Menlo

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