I have splitor shapedmonolithsbefore.I have a sideproject thatI’mpassionateabout.I’veparticipated ina communityevent ormeetup.I startedcodingbefore Iwas 16.I’ve used atleast threedifferentIDEs/editors.I’vementored ortaughtsomeonehow to code.I prefermonolithicarchitectureovermicroservices. I can name afavoritesoftwaredevelopmentbook.I alwaysuse darkmode.I write myunit testsfirst.I’ve codedinassemblylanguage.I prefer usinga terminalover agraphicalinterface.I can name atleast fiveprogramminglanguages.I’vedeployedcode on aFridayevening.I love pairprogramming.I workedremotelybefore it wascommon.I have a “warstory” from ahigh-stakesproject ordeadline.I’ve attendedmore thanthreeengineeringconferences.I’ve contributedto an open-source projectother than ourown.I’ve brokenproductionat leastonce.I’ve workedon a privateproject formore than ayear.I know how towrite in morethan threeprogramminglanguages.I can explainthe differencebetweenREST andGraphQL.I enjoydebuggingmore thancoding newfeatures.I have splitor shapedmonolithsbefore.I have a sideproject thatI’mpassionateabout.I’veparticipated ina communityevent ormeetup.I startedcodingbefore Iwas 16.I’ve used atleast threedifferentIDEs/editors.I’vementored ortaughtsomeonehow to code.I prefermonolithicarchitectureovermicroservices. I can name afavoritesoftwaredevelopmentbook.I alwaysuse darkmode.I write myunit testsfirst.I’ve codedinassemblylanguage.I prefer usinga terminalover agraphicalinterface.I can name atleast fiveprogramminglanguages.I’vedeployedcode on aFridayevening.I love pairprogramming.I workedremotelybefore it wascommon.I have a “warstory” from ahigh-stakesproject ordeadline.I’ve attendedmore thanthreeengineeringconferences.I’ve contributedto an open-source projectother than ourown.I’ve brokenproductionat leastonce.I’ve workedon a privateproject formore than ayear.I know how towrite in morethan threeprogramminglanguages.I can explainthe differencebetweenREST andGraphQL.I enjoydebuggingmore thancoding newfeatures.

Engineering Bingo - 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. I have split or shaped monoliths before.
  2. I have a side project that I’m passionate about.
  3. I’ve participated in a community event or meetup.
  4. I started coding before I was 16.
  5. I’ve used at least three different IDEs/editors.
  6. I’ve mentored or taught someone how to code.
  7. I prefer monolithic architecture over microservices.
  8. I can name a favorite software development book.
  9. I always use dark mode.
  10. I write my unit tests first.
  11. I’ve coded in assembly language.
  12. I prefer using a terminal over a graphical interface.
  13. I can name at least five programming languages.
  14. I’ve deployed code on a Friday evening.
  15. I love pair programming.
  16. I worked remotely before it was common.
  17. I have a “war story” from a high-stakes project or deadline.
  18. I’ve attended more than three engineering conferences.
  19. I’ve contributed to an open-source project other than our own.
  20. I’ve broken production at least once.
  21. I’ve worked on a private project for more than a year.
  22. I know how to write in more than three programming languages.
  23. I can explain the difference between REST and GraphQL.
  24. I enjoy debugging more than coding new features.