v Plan early and expect the unexpected. Make sure your team has a clear and straightforward idea on your project. Don’t demand too much on your project, just use the wealth of knowledge that you learned thus far and apply it to make a great 218A project.

v Spend some time on your pseudo-code. It will do wonders down the road in making your code to function the way you want it to and it will help with documentation.

v Perform your best to meet the milestones. Don’t just make a simple circuit schematic that looks like it will work. Perform calculations at the beginning to make it close to the actual circuit when built because your circuit schematics are one of the most important aspects during the project for the design, debugging, and final documentation. The schematics will always be with you, so make them good and readable.

v Past years always recommend to hot glue or provide some other means in fixing your wiring to the protoboard. It really shouldn’t be a suggestion, it should be a requirement. It doesn’t have to be for all your wiring, but the ones that keep on coming loose. It will remove something off your list in why your project is not working.

v Spend some time making your project presentable. For presentation night, a lot of kids show up. If your game “looks” fun to play, then you’ll attract more players and have a lot of happy customers

v Don’t wait for one thing to do another thing. Work together as a group and divide the work that will complete the tasks for enough time to integrate everyone’s work. Save room after building for debugging. Work over the holidays if necessary because right after the break, it’s showtime!