(5 intermediate revisions by 2 users not shown) | |||
Line 7,481: | Line 7,481: | ||
− | <div class="row" style="padding-left:50px; padding-bottom: 10px;"> | + | <div class="row" style="padding-left:50px; padding-bottom: 10px; padding-right:50px"> |
− | + | <br><br> | |
− | To iGEMers who read this page,< | + | <h4> |
+ | To iGEMers who read this page,</h4> | ||
+ | |||
+ | <h5 style="position:top"> | ||
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. | 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. | ||
Line 7,494: | Line 7,497: | ||
<br><br> | <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. | 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> | |
− | + | ||
+ | </h5> | ||
+ | |||
</div> | </div> | ||
− | <div class="row" style="padding-left:50px; padding-bottom: 10px;"> | + | <div class="row" style="padding-left:50px; padding-bottom: 10px; padding-right:50px"> |
<h5 style="position:top"> | <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> | 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> | ||
− | + | <br><br> | |
+ | <br><br> | ||
+ | <h5>Hallo! This is Lucinda Lin with something else to add: <br><br> | ||
+ | |||
+ | 5. Communication is important! When you feel that iGEM has negatively impacted your academics or relationships with your family, do tell your teammates and see whether | ||
+ | they can help you by sharing some of your tasks. Don't take up more tasks than you can finish and then overwork yourself, because the result is often not satisfying for both you and the team. | ||
+ | <br><br> | ||
+ | 6. Checking on previous teams' wikis is a good way to get to know iGEM better and find inspiration. However, you should know that some of the contents have been revised after the competition. For example, we use external links to share our presentation powerpoints and merge the hardware and public engagement pages based on <a href="https://static.igem.org/mediawiki/2018/a/af/T--GreatBay_China--Judge.pdf">judging feedbacks.</a>. | ||
+ | <br><br> | ||
+ | 7. Keep in touch with the HQ and safety commitee! They kindly answered our questions on criteria and biosafety & ethics throughout the competition. | ||
+ | </br></br></h5> | ||
+ | <h4> | ||
+ | You can find our team email at the bottom of this page. Feel free to contact us through email or twitter!<br> | ||
+ | </h4> | ||
</div> | </div> | ||