purecheddar"its justonefunction"asyncfor noreason;velasquezcodepatternawaitingsomethingthat isnt apromiseif(condition)forgot toescaperegexused varinsteadof letdeleted allthesourcecodedidn'tuse alambdarandomlymakes ita moduledidn't uselibrarythat doesit allmissingawaitrandomcsyntaxdoesn'thave alinternamedvariable"x"didn'treaddocsdidn't useeventhandlersmalformedhtmlreadingwrongpart of thedocsregexfailed tomatchpermissionissuemissing`function`purecheddar"its justonefunction"asyncfor noreason;velasquezcodepatternawaitingsomethingthat isnt apromiseif(condition)forgot toescaperegexused varinsteadof letdeleted allthesourcecodedidn'tuse alambdarandomlymakes ita moduledidn't uselibrarythat doesit allmissingawaitrandomcsyntaxdoesn'thave alinternamedvariable"x"didn'treaddocsdidn't useeventhandlersmalformedhtmlreadingwrongpart of thedocsregexfailed tomatchpermissionissuemissing`function`

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