too many parameters Data included in git repo do_fooBarandBaz hand rolled implementation of builtin behaviour "../../../foo" idioms from other languages (bonus if FORTRAN) fractal if statements changes CWD at random points # increment counter counter += 1 little to no build instructions print("here!") if (false){ commented out code Hardcoded paths reference developer laptop many empty doc pages abbreviations # last run 13- 03-2022 routine use cases require editing code # TODO: fix after release mixture of old and new coding style comment clarifies what code does but not why hard coded versions Empty README.md random closures too many parameters Data included in git repo do_fooBarandBaz hand rolled implementation of builtin behaviour "../../../foo" idioms from other languages (bonus if FORTRAN) fractal if statements changes CWD at random points # increment counter counter += 1 little to no build instructions print("here!") if (false){ commented out code Hardcoded paths reference developer laptop many empty doc pages abbreviations # last run 13- 03-2022 routine use cases require editing code # TODO: fix after release mixture of old and new coding style comment clarifies what code does but not why hard coded versions Empty README.md random closures
(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.
too many parameters
Data included in git repo
do_fooBarandBaz
hand rolled implementation of builtin behaviour
"../../../foo"
idioms from other languages (bonus if FORTRAN)
fractal if statements
changes CWD at random points
# increment counter
counter += 1
little to no build instructions
print("here!")
if (false){
commented out code
Hardcoded paths reference developer laptop
many empty doc pages
abbreviations
# last run 13-03-2022
routine use cases require editing code
# TODO: fix after release
mixture of old and new coding style
comment clarifies what code does but not why
hard coded versions
Empty README.md
random closures