The DSA Curriculum

This repository is for the excos to upload their curriculum materials for future sub-comms to use. Please feel free to fork this repository for your own use!

The Timeline

Python Recap

{
  "Topic":"A refersher on Python syntax, as well as on EDA and Data Visualisation techniques using Python.",
  "Dates":"1/10/24", "3/10/24", "8/10/24"
  "Lecturers":"Abhishek"
}

---

SQL Recap

{
  "Topic":"A referesher on SQL syntax, as well as on advanced SQL functions",
  "Dates":"10/10/24",
  "Lecturers":"Jun Yeow"
}

---

GenAI

{
  "Topic":"Understanding the theory behind Generative AI models and learning to code with them practically",
  "Dates":"15/10/24", "17/10/24", "22/10/24"
  "Lecturers":"Jun Yeow"
}

---

Deep Learning

{
  "Topic":"A deep dive into understanding and building complex Neural Networks to solve a variety of problems and use cases, with a brief look into other ML algorithms",
  "Dates":"24/10/24", "29/10/24", "12/11/24", "14/11/24", "19/11/24"
  "Lecturers":"Abhishek"
}

---

Advanced SQL

{
  "Topic":"A deep dive into advanced SQL techniques, with an emphasis on query optimisation techniques for a plethora of case studies",
  "Dates":"21/11/24", "26/11/24", "3/11/24", "5/11/24"
  "Lecturers":"Jun Yeow and Abhishek"
}

---

Amazon Web Services Workshop

{
  "Topic":"TBD",
  "Dates":"5/11/24", "7/11/24"
  "Lecturers":"Jun Yeow, Luqman, Jaryl, Abhishek, Geneiveve, Kaavya, and Cheryl"
}

---

Internal Projects Session

{
  "Topic":"Subcomms will be divided into teams and tasked to create a project which solves a certain problem or fulfills a certain requirment within the deadline. The entire group will then be asked to present their submission to the rest of the club.",
  "Dates":"27/11/24 to 18/12/24"
}

---

Setting up VSCode

VSCode stands for Visual Studio Code, which is an Integrated Development Environment (IDE), which basically means its a software which can read, write and run code files in several different programming languages.

If you need to download data files for your curriculum lecture, you can find them here: https://drive.google.com/drive/folders/1CHD58vL4TLSvLfrnw0Mh_-EAqkNBUMVH?usp=sharing

1. Install Visual Studio Code from https://code.visualstudio.com/

2. Install Anaconda from https://www.anaconda.com/download

3. Open Visual Stuido Code, go to the extensions tab on the activity bar, and download the the following extensions:

• Make sure all of these extensions are by Microsoft:
  • Python
  • Jupyter
  • GitHub Pull Requests

4. Install Pip by running the command "python3 get-pip.py" in your termninal window.

5. Congratulations! You are now ready to code!

Forking the curriculum

In GitHub, "forking a repository" means to create a copy of all the files within a certain repository for your own GitHub account. For example, you can "fork" this repository to create a personal copy of the DAC curriculum materials inside your GitHub account.

If you need a more visual guide to understand how to fork a repository, you can find it here: https://scribehow.com/shared/Forking_the_DACDSA_Curriculum_Repository__uJ4bd99_TTWagei2bQgC1Q

1. Fork the Repository on GitHub:

• Click on the GitHub link shared, which will open the repository in web browser.
• Click the "Fork" button at the top right corner of the repository page.

This will create a personal copy of the repository under your GitHub account.

2. Clone the Forked Repository to VSCode:

• Open VSCode:
• Open the Command Palette:
  • Press "Ctrl + Shift + P" (or "Cmd + Shift + P" on Mac) to open the Command Palette.
• Clone the Repository:
  • Type "Git: Clone" and select it.
  • Paste the URL of your forked repository from your GitHub account and choose a local folder where you want to save the repository.
• Open the Repository:
  • Once the repository is cloned, VSCode will prompt to open the repository. Click "Open" to open the project in VSCode.

3.Explore and Work on the Materials:

• you can now browse through the folders and files in the repository from the VSCode sidebar.

4. Open Files and Edit:

• They can open any .py or .ipynb files and start working on the exercises, making changes in your local copy.

5. Run the Code:

• To run Python scripts, you can right-click the file and choose “Run Python File in Terminal” or use the run button at the top right corner.
• For Jupyter notebooks (.ipynb files), you can run the cells directly in VSCode if the Jupyter extension is installed.

6. Commit Changes Locally:

• Make Changes: you can make changes to the files as you work through the exercises.
• Stage and Commit Changes: In the Source Control tab, you can stage your changes (click on the +icon next to each file) and commit with a message (e.g., “Completed exercise 1”).

7. Push Changes to Their Forked Repository:

• Push to GitHub: After committing changes, you can push the changes to your forked repository on GitHub by clicking the "Sync Changes" button in the Source Control tab.
• This allows you to save your progress online without affecting the original repository.