Dossier Advice

From WLCS
Revision as of 11:20, 5 April 2011 by Admin (talk | contribs)

2010 - 2011

  • Daniel Browning - "Focus on the sections and keep them consistent"
  • Alex/John Cummins - ""
  • Brendan Ritter - "The sections are more important than the code or what it does"
  • Peter Vernia - "Make your revisions early"
  • Solomon Hailu - "Keep your dossier simple"
  • Ian McLennan - ""
  • Robert Mercado - "Don't lose your USB flash drive"
  • Kibret Tsige - "The sections outline your project, so get them done first"
  • John [JP] Heng - ""
  • Shengyuan Wang - "Be sure to choose simple dossier"
  • Arati Sharma - "Don't try to change your code at the last minute"
  • Scarlet Jaldin - "Quality over quantity. Straight and to the point. Follow everything listed in the rubrics."
  • Sara Neel - "You can work for 12 hours straight the night before and *still* not be done. (i.e. don't procrastinate)"
  • Teddy Peneva - "Save everything you do."
  • Paulo Dorado - "Do it seriously, and don't half-arse it"
  • Rene Ochoa - ""
  • Nick Hallowell - ""
  • Matt Hines - "Do it efficiently."
  • Mr. Bui - "Avoid copying other peoples' work without thinking b/c chances are, you *both* will have bad dossiers"

2009 - 2010

  • Iver Altamirano - "Don't procrastinate"
  • Drake Anderson - "Umm. Choose a topic that interests you"
  • Jason Andrade - "Aaahhh. Finish the code within the first month"
  • Nick Apseloff - "Work hard on your sections early on in the year because you won't want to do them later"
  • Josh Braden - "Focus on good initial design so you don't have to redo everything"
  • Suchana Costa - "Use all the class time you can!"
  • Oliver De La Via - "Do not make these mistakes:"
    • "Do little coding due to having other hw for 3 months (sacrifice that sleep every so often early in the year rather than at the last minute)"
    • "Not making a copy of each file (the file can be lost or inaccessible, in my case"
    • "Not believe Mr. Bui when he says that a student spent 3 days straight coding even though he was a good coder (I spent more than 5 days and still am not done)"
    • "Think you can finish this in the last week alone (you will have other hw and IAs to turn in)"
  • Ian Feeney - "Don't slack on the Mastery Aspects. Do them correctly."
  • Matt Hines - "Do it right the first time (earlier in the year)"
  • Sean Hoffman - "Stick with one program idea, and don't constantly keep changing it"
  • Paul Johnson - "Manage your time"
  • Alex Lindeman - "Don't try to pay somebody to do your dossier for you"
  • Reuben Luoma-Overstreet - "Look at the mastery aspects before you code"
  • Abdullah Mamun - "Look at previous sections when you work on any of them."
  • Arnold Montecinos - "Don't limit yourself to only what you learned in class."
  • Matt Newman - "SL is for n00bz"
  • Trevor Newton - "Don't completely BS sections if you want any sleep later"
  • Matt Pearson-Beck - "Don't make your idea too complicated because you won't know how to code it as well as you think you will be able to"
  • Aasim Rawoot - "Do a binary tree because you will be rewarded later"
  • Manik Sarik - "Sit next to a helpful student"
  • Zol Tsogoo - "Do your work on time! Don't get a job where you'll have to do your stuff at night"
  • Ben Whelan - "It's impossible to complete at the last minute."
  • Mr. Bui - "If you wait until the last minute, you will not complete it well, and by well, I mean it will be teh suck"