Difference between revisions of "Team:NAIT Edmonton/Practices"

Line 281: Line 281:
 
<p>Many of the design principles used to design your wiki can also be applied to your poster and presentation. In fact, having some sort of recurring theme and unity between your wiki, presentation and poster. For example, using the same colour scheme and logos would connect all of your platforms together. </p> <br>
 
<p>Many of the design principles used to design your wiki can also be applied to your poster and presentation. In fact, having some sort of recurring theme and unity between your wiki, presentation and poster. For example, using the same colour scheme and logos would connect all of your platforms together. </p> <br>
  
In Summary: <br>
+
In Summary: <br><br>
 +
 
 
<ol>  
 
<ol>  
 
   <li>Content. Content. Content. </li>
 
   <li>Content. Content. Content. </li>
Line 290: Line 291:
 
</ol>
 
</ol>
  
<br><br>
+
<br>
 
</div><!--end .accordion-section-content-->
 
</div><!--end .accordion-section-content-->
 
</div><!--end .accordion-section-->
 
</div><!--end .accordion-section-->

Revision as of 23:30, 31 August 2015

Team NAIT 2015

Human Practices

What type of work does it take to get to the Jamboree? What do you need to know? We reached out to teams across the world to get their perspective on their iGEM journey and compiled the information so that future teams can draw from our collective experiences and learn!

Content on this page is coming soon!

Introduction

"Anything that can go wrong, will go wrong" – Murphy’s Law

We often find that even though we try to account for every potential problem, there is always one that should have been obvious. This scenario is inevitable and more often than not, will happen at the worst time possible. How we handle these unforeseen problems can result in either a successful mission or a critical mission failure. As a team competing for the first time, there was no shortage of these scenarios and as a good team should, we came together and quickly found solutions for the problems. As the summer passed, our knowledge and experience grew and we decided to reach out to the teams in our track to compile all of our collective experiences and perspectives on the iGEM experience and put it together to create a tool for future team’s use.


In this guide you will find multiple team’s perspective on topics such as design, laboratory work, funding, team building and the suggested approach to potential problems that can emerge. However, our vision for this guide is to not only provide insight and solutions to some of these unforeseen problems but to also challenge the way in which we perform established practices used in the preparation for the iGEM competition. In future we hope to evolve this guide into a forum where all iGEM teams can contribute to each other’s knowledge, because we believe the main goal of the iGEM competition, at its core, is to provide students with an opportunity to learn and grow the scientific community.

Project Design

"Every project is an opportunity to learn, to figure out problems and challenges, to invent and reinvent." - David Rockwell

So you’ve heard about this competition called iGEM and you are raring to go! But before you hit the labs, you need an idea for a project, so how do you actually get an idea? Through interviewing some of the teams we found that there was a few methods you can use to come up with an idea to pursue for the competition.


This year will our first time competing in the iGEM competition and despite looking at previous teams’ work we were having difficulty choosing a project. We started this planning in late spring and with summer quickly approaching, what would we do?


We decided to rely on our mentor Dr. Marcelo Marcet for inspiration for a project. He provided us with a few ideas, and after reviewing them we decided on one that was both practical and had potential for future applications.


In an interview we had with Dr. Marcet, he had this advice to give; “For a good project design, you need two things, knowledge and experience. Knowledge comes from our education and experience comes from actually experiencing the challenges. By combining these two together we can not only come up with a solution to the problem but also appreciate it.”


As first time iGEM’s this advice resonated with us. By learning from him and gaining experience by practicing synthetic biology, we can apply this thinking to not only the iGEM competition but also to any organisation we are a part off.

Wiki and Design Concepts

"Design is not just what it looks like and feels like. Design is how it works." - Steve Jobs

The communication of our ideas and project before the Jamboree is mostly done on our Wikis. Many of the judges, prior to attending a presentation session, will check the team’s Wiki to ready themselves for the technical talk and to gain a first look and a basic understanding of the project. Additionally, as it is accessible by all, the Wiki can be used as a platform to introduce projects and synthetic biology to the general public. How the Wiki is designed and how it conveys information is therefore extremely important not only for the iGEM competition, but also for how your project is perceived in society’s eye. “When you do things right, people won’t be sure you’ve done anything at all.” When people visit your Wiki, you want them to read and enjoy the content you’ve provided. People can inherently tell if there is something off about your design. If your wiki delivers all the necessities and no one can point out a flaw, you’ve done your job. Designing a functional Wiki was one of the hardest things our team had to tackle. In addition to the complexity of HTML, Java, and CSS (to say the least) we also had to make sure our content was readable and fun to learn. Essentially, your Wiki is an extension of your presentation. Your Wiki is the first impression that you are going to give the judges and anyone else who happens to stumble upon the iGEM site. Your Wiki is important. It is not something you should leave to the last minute. Start on it early and make sure you back up everything you do!


Many of the design principles used to design your wiki can also be applied to your poster and presentation. In fact, having some sort of recurring theme and unity between your wiki, presentation and poster. For example, using the same colour scheme and logos would connect all of your platforms together.


In Summary:

  1. Content. Content. Content.
  2. Readers are lazy. Make finding information easy.
  3. Make learning your project fun.
  4. Organize content logically.
  5. Less is more. Simple is the way to go.