velasquezcodepatternreadingwrongpart of thedocs"its justonefunction"regexfailed tomatch;malformedhtmldidn'tuse alambdadoesn'thave alinterdidn'treaddocsif(condition)purecheddarused varinsteadof letmissing`function`missingawaitdeleted allthesourcecodedidn't useeventhandlersrandomlymakes ita modulenamedvariable"x"randomcsyntaxforgot toescaperegexawaitingsomethingthat isnt apromisedidn't uselibrarythat doesit allasyncfor noreasonpermissionissuevelasquezcodepatternreadingwrongpart of thedocs"its justonefunction"regexfailed tomatch;malformedhtmldidn'tuse alambdadoesn'thave alinterdidn'treaddocsif(condition)purecheddarused varinsteadof letmissing`function`missingawaitdeleted allthesourcecodedidn't useeventhandlersrandomlymakes ita modulenamedvariable"x"randomcsyntaxforgot toescaperegexawaitingsomethingthat isnt apromisedidn't uselibrarythat doesit allasyncfor noreasonpermissionissue

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