Open sourceinstallblocked bysecurity1x1 w.leadershipcancelledTranslationassumed towork inlanguageswe've nevertestedFine-tuningignored assolution tocurrentproblemsTaskassigned tome in thirdpersonSomeonesuggests alanguagemodel from<= 2023I pushfeature toprod after 15mins of localtesting"Multi-agent"mentionedwithoutplausible tasksfor agentsOther project givenridiculous amount ofslack despite obviousdysfunction and path tofailure. Special rule: Tokenizercannot count towardsthis spaceAfter hourstech supporton "non-prod" systemEngineeringdecisionbased offnews cycleExpectationsset in directcontradictionto what I justsaidZero-contextmeeting with newteam to bringcustom use caseto production withno money nocommitmentFine-tuningreferencedto solvefutureproblemsQuantizedmodelreferred toas basemodelCity of Amarillomentioned asDH successwhile stillunfinishedAssumptionthat LLMs knoweverything via"downloadingthe internet" orsomethingTroubleshootdemo withoutdata ordescription ofscope"SLM"mentionedwithout anyreference tosizeNo timelineor prioritylevel givento taskExpectationsbased onthat one timeit workedHigh stakeslive demowith noprior testingNon-technicalpersonsuggests I trypromptengineeringEngineeringdecisionbased offpowerpointOpen sourceinstallblocked bysecurity1x1 w.leadershipcancelledTranslationassumed towork inlanguageswe've nevertestedFine-tuningignored assolution tocurrentproblemsTaskassigned tome in thirdpersonSomeonesuggests alanguagemodel from<= 2023I pushfeature toprod after 15mins of localtesting"Multi-agent"mentionedwithoutplausible tasksfor agentsOther project givenridiculous amount ofslack despite obviousdysfunction and path tofailure. Special rule: Tokenizercannot count towardsthis spaceAfter hourstech supporton "non-prod" systemEngineeringdecisionbased offnews cycleExpectationsset in directcontradictionto what I justsaidZero-contextmeeting with newteam to bringcustom use caseto production withno money nocommitmentFine-tuningreferencedto solvefutureproblemsQuantizedmodelreferred toas basemodelCity of Amarillomentioned asDH successwhile stillunfinishedAssumptionthat LLMs knoweverything via"downloadingthe internet" orsomethingTroubleshootdemo withoutdata ordescription ofscope"SLM"mentionedwithout anyreference tosizeNo timelineor prioritylevel givento taskExpectationsbased onthat one timeit workedHigh stakeslive demowith noprior testingNon-technicalpersonsuggests I trypromptengineeringEngineeringdecisionbased offpowerpoint

CTO WEEKLY BINGO - 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. Open source install blocked by security
  2. 1x1 w. leadership cancelled
  3. Translation assumed to work in languages we've never tested
  4. Fine-tuning ignored as solution to current problems
  5. Task assigned to me in third person
  6. Someone suggests a language model from <= 2023
  7. I push feature to prod after 15 mins of local testing
  8. "Multi-agent" mentioned without plausible tasks for agents
  9. Other project given ridiculous amount of slack despite obvious dysfunction and path to failure. Special rule: Tokenizer cannot count towards this space
  10. After hours tech support on "non-prod" system
  11. Engineering decision based off news cycle
  12. Expectations set in direct contradiction to what I just said
  13. Zero-context meeting with new team to bring custom use case to production with no money no commitment
  14. Fine-tuning referenced to solve future problems
  15. Quantized model referred to as base model
  16. City of Amarillo mentioned as DH success while still unfinished
  17. Assumption that LLMs know everything via "downloading the internet" or something
  18. Troubleshoot demo without data or description of scope
  19. "SLM" mentioned without any reference to size
  20. No timeline or priority level given to task
  21. Expectations based on that one time it worked
  22. High stakes live demo with no prior testing
  23. Non-technical person suggests I try prompt engineering
  24. Engineering decision based off powerpoint