This bingo card has a free space and 24 words: Fixed a bug and do not fully understand why it worked, Accidentally closed my IDE without saving my work, Wrote a bug while trying to fix another bug in the codebase, Left a funny comment in the code for future readers to find, Went to a tech talk or info session for the free food or swag, Changed my major at least once, Started an assignment the night before it was due, Used Git and got stuck in merge conflict issues, Used AI to explain an error message, Broke something while refactoring code to make it cleaner, Said we will fix it later and never actually fixed it, Shipped a feature and immediately found a bug afterward, Copied code from Stack Overflow, Forgot a semicolon and broke everything, Spent 30+ minutes debugging and it was a typo, Forgot to handle an edge case and everything crashed, Wrote a solution that was correct but too slow for the constraints, Practiced coding interview questions on LeetCode, Forgot to pull before pushing changes, Had more than twenty browser tabs open while coding, Searched ‘how to center a div’ more than once, Attended a hackathon, Built something small just for myself such as a script, website, or bot and Got a runtime error I had never seen before.
Assignment Guru Bingo! | DOMINGO | HackByte 3.0 Bingo | QA | CS Bingo
Share this URL with your players:
For more control of your online game, create a clone of this card first.
Learn how to conduct a bingo game.
With players vying for a you'll have to call about __ items before someone wins. There's a __% chance that a lucky player would win after calling __ items.
Tip: If you want your game to last longer (on average), add more unique words/images to it.
