malformedhtmlvelasquezcodepatternmissingawaitawaitingsomethingthat isnt apromisedidn'treaddocsif(condition)didn'tuse alambdapurecheddardidn't uselibrarythat doesit alldeleted allthesourcecodenamedvariable"x"regexfailed tomatchrandomcsyntaxmissing`function`readingwrongpart of thedocsused varinsteadof letdoesn'thave alinter;asyncfor noreasondidn't useeventhandlersforgot toescaperegexpermissionissue"its justonefunction"randomlymakes ita modulemalformedhtmlvelasquezcodepatternmissingawaitawaitingsomethingthat isnt apromisedidn'treaddocsif(condition)didn'tuse alambdapurecheddardidn't uselibrarythat doesit alldeleted allthesourcecodenamedvariable"x"regexfailed tomatchrandomcsyntaxmissing`function`readingwrongpart of thedocsused varinsteadof letdoesn'thave alinter;asyncfor noreasondidn't useeventhandlersforgot toescaperegexpermissionissue"its justonefunction"randomlymakes ita module

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