Line 7,480: | Line 7,480: | ||
</div> | </div> | ||
+ | |||
+ | <div class="row" style="padding-left:50px; padding-bottom: 10px;"> | ||
+ | <h5 style="position:top"> | ||
+ | To iGEMers who read this page,<br><br> | ||
+ | |||
+ | Hi iGEMers! This is Alexis Zeng writing to you. And as you can see on the home page: we actually did pretty well this year! Therefore I also want to share some tips which helped us a great deal, and high school teams especially might find them useful. | ||
+ | <br><br> | ||
+ | 1. Don’t miss any important deadlines. Deadlines of Part submission, judging form freeze, and the final wiki freeze are soooo vital if you want to win medals. Although it doesn’t affect how good your project is, it’s still better to keep an eye on them. Shared calendar is a helpful tool to make sure everyone in the team is aware of the deadlines. | ||
+ | <br><br> | ||
+ | 2. Actively reach out for help. Obstacles and mysteries are inevitable, but you are not alone. Be brave to seek assistance from your advisors, PIs, other PIs, and literally anyone is relevant or is able to connect you with more resources. And when in doubt about rules or safety issues, it’s a good idea to write to the HQ. Active communication is an excellent solution for everything. | ||
+ | <br><br> | ||
+ | 3. Start early. We began the project in March, which gave us more abundant time compared to those who start in the summer and allowed us to complete this huge project. | ||
+ | <br><br> | ||
+ | 4. Read the judging handbook ahead. In my opinion, the judging handbook provides clear guidance to design a good project: it includes good examples from previous years; some aspects likely to be neglected when designing; how would the judges assess your project. | ||
+ | <br><br> | ||
+ | You can find our team email at the bottom of this page. Feel free to contact us through email or twitter!<br> | ||
+ | </div> | ||
− | + | <div class="row" style="padding-left:50px; padding-bottom: 10px;"> | |
+ | <h5 style="position:top"> | ||
+ | Charles would like to agree every points Alexis mentioned above. In addition, documentation of your project, HP, and labwork is also important. It will make life easier when you comes to the end of the project. Engaging in meetups and talking to other teams can give you some valuable and unexpected advices. </h5> | ||
+ | </h5> | ||
+ | </div> | ||