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

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