Overall, the Blackjack code was a success. When the final program was tested, all of the main components of the game worked very well with no apparent bugs. The team was able to add components to the game that they believed would not originally possible, but were efficient enough in coding to make it happen. Breaking down a big problem into several smaller problems was a great problem solving strategy because it made a daunting task more realistic and would produce the desired end result. If any changes were to be made, a deck of cards that has four graphically represented suits would have been added to ease readability and make it more like a card game. Unfortunately, the deck of cards was initially made without suits and graphics were not able to be efficiently programmed into the game due to time. Another recommendation to create this game more efficiently would be to plan out the program more before hand. Several unforeseen problems arose in the game while coding, so it threw the team off track. If these problems were planned for, they would have been expected and when they came up, it wouldn’t have been as overwhelming.