namedvariable"x"purecheddar"its justonefunction"randomcsyntaxmissing`function`awaitingsomethingthat isnt apromisedidn't uselibrarythat doesit alldeleted allthesourcecodevelasquezcodepatternmalformedhtml;didn't useeventhandlersregexfailed tomatchif(condition)doesn'thave alinterreadingwrongpart of thedocsrandomlymakes ita modulepermissionissuedidn'treaddocsdidn'tuse alambdaasyncfor noreasonused varinsteadof letforgot toescaperegexmissingawaitnamedvariable"x"purecheddar"its justonefunction"randomcsyntaxmissing`function`awaitingsomethingthat isnt apromisedidn't uselibrarythat doesit alldeleted allthesourcecodevelasquezcodepatternmalformedhtml;didn't useeventhandlersregexfailed tomatchif(condition)doesn'thave alinterreadingwrongpart of thedocsrandomlymakes ita modulepermissionissuedidn'treaddocsdidn'tuse alambdaasyncfor noreasonused varinsteadof letforgot toescaperegexmissingawait

Luke Debugging - 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. named variable "x"
  2. pure cheddar
  3. "its just one function"
  4. random c syntax
  5. missing `function`
  6. awaiting something that isnt a promise
  7. didn't use library that does it all
  8. deleted all the source code
  9. velasquez code pattern
  10. malformed html
  11. ;
  12. didn't use event handlers
  13. regex failed to match
  14. if(condition)
  15. doesn't have a linter
  16. reading wrong part of the docs
  17. randomly makes it a module
  18. permission issue
  19. didn't read docs
  20. didn't use a lambda
  21. async for no reason
  22. used var instead of let
  23. forgot to escape regex
  24. missing await