This site is from a past semester! The current version is here.
CS2113/T Aug '19
  • Week 1 [Aug 12]
  • Week 2 [Aug 19]
  • Week 3 [Aug 26]
  • Week 4 [Sep 2]
  • Week 5 [Sep 9]
  • Week 6 [Sep 16]
  • Week 7 [Sep 30]
  • Week 8 [Oct 7]
  • Week 9 [Oct 14]
  • Week 10 [Oct 21]
  • Week 11 [Oct 28]
  • Week 12 [Nov 4]
  • Week 13 [Nov 11]
  • Textbook
  • Admin Info
  • Report Bugs
  • Slack
  • Forum
  • Project Info
  • Instructors
  • Announcements
  • File Submissions
  • Tutorial Schedule
  • Duke
  • Project Phase1 Dashboard
  • Java Coding Standard
  • samplerepo-things
  • Projects List
  • config.json templates for Reposense
  • PersonalAssistant-Duke
  • Project Phase2 Dashboard
  • Reference project - Addressbook
  • Repl.it classroom
  • Previous WeekNext Week

    Week 6 [Sep 16]

    💰 A note on participation points

    After reaching 15 participation points:

    • We encourage you to continue to do module activities (irrespective of whether they have participation points) because every time you skip a module activity, it can potentially make the remainder of the module a harder for you to follow, due to the highly-connect and iterative nature of this module.

    Participation points will be released after recess week

    • We will wait for the first peer review to complete before releasing the participation points.

    🆘 Seeking help

    If you need help

    • Do inform your tutor (or write to the module email) if you are falling behind or cannot cope with the module requirements. While we try to avoid hand holding or spoon feeding students, we do want to help you keep up with the module pace when necessary.

    Using third party libraries

    You are allowed to use third-party libraries subject to the constraints below:

    • It should be an open-source project, STRICTLY NO FREEWARE binaries!
      • There may be some exceptions, decided on a case-to-case basis.
      • Which means you cannot use random code from your friend in the project.
    • Either you or the users should not be required to pay for using the library.
    • The library should be released under a permissive license (MIT/Apache 2.0 are most preferred).
    • You need to seek permission by listing the library here before you can use it.
    • Once the library is approved for one team, it is approved for the entire class. No need to ask permission again!
    • You need to acknowledge the use of such libraries explicitly in your project documentation that is publicly visible.
      • E.g., In the landing page of your project (or README.md file on GitHub), developer guide, etc.