Everyone:

Next week, we will provide a brief overview of the course and then dive into reviewing performing basic I/O in C, C++, and Python. Next, we will refresh our understanding of algorithmic complexity before discussing sequence containers such as arrays, lists, stacks, and queues. While these are rather basic data structures, it is important to understand their properties and behavior, which we will take advantage of in Challenge 01, Challenge 02, and Challenge 03.

We will also discuss good coding style and the use of linters to analyze source code.

Reading

The readings for Monday, June 3 are

1. Competitive Programmer's Handbook

   • Chapter 1 Introduction

   • Chapter 2 Time Complexity

   • Chapter 4 Data Structures

2. Interview Cake

   • Array

   • Dynamic Array

   • Linked List

   • Stack

   • Queue

Optional

If you are interested in knowing a little more about C++ auto loops, then check out the following:

1. Ranged-based for Statement (C++)

2. Iterators

If you are interested in knowing how to utilize lists in Python as stacks and queues, the check out the following:

1. Data Structures - More on Lists

Quiz

Once you have done the readings, answer the following Reading 01 Quiz questions:

To submit your answers, you will need create a answers.json or answers.yaml file in the reading01 folder of your assignments repository:

1. For this class, you must use a separate git branch for each assignment. This means that the work for each reading and challenge must be done in a separate branch. To create and checkout a new branch, you can do the following:

   $ git checkout master         # Make sure we are in master branch
   $ git pull --rebase           # Make sure we are up-to-date with GitLab repository
   
   $ git checkout -b reading01   # Create reading01 branch and check it out
   

   Once you do the above, you should see the following output for the git-branch command:

   $ git branch
     master
   * reading01
   

   The * indicates that we are currently on the reading01 branch.

2. You can either hand-write the answers file using your favorite text editor or you can use the online form to generate the JSON data.

   A hand-written answers.yaml may look like the following:

   q1:     [python,perl,ruby]
   q2:     [n2,nf,nlogn,1,n,sqrtn,logn]
   q3:     n
   q4:     n
   

   The equivalent answers.json generated using the online form may look like the following:

   {
     "q1": [
       "python",
       "perl",
       "ruby"
     ],
     "q2": [
       "n2",
       "nf",
       "nlogn",
       "1",
       "n",
       "sqrtn",
       "logn"
     ],
     "q3": "n",
     "q4": "n"
   }
   

   You may use either format. To determine which symbols correspond to which response, take a look at the Reading 01 Quiz file.

   To check your answers, you can use the provided .scripts/submit.py script:

   $ cd reading01                        # Go into reading01 folder
   $ $EDITOR answers.json                # Edit your answers.json file
   
   $ ../.scripts/submit.py               # Submit reading01
   Submitting reading01 assignment ...
   Submitting reading01 quiz ...
         Q1 0.14
         Q2 0.14
         Q3 0.00
         Q4 0.00
         Q5 0.00
         Q6 0.00
         Q7 0.00
         Q8 0.00
      Score 0.29
   

   This script will submit your reading01/answers.json file to dredd, which is the automated grading system. dredd will take your answers and return to you a score as shown above. Each reading is worth 2.0 points.

   Note: You may submit your quiz answers as many times as you want; dredd does not keep track of who submits what or how many times. It simply returns a score.

3. Once you have your answers file, you need to add, commit the file, and push your commits to GitLab:

   $ git add answers.json                # Add answers.json to staging area
   $ git commit -m "Reading 00: Done"    # Commit work
   
   $ git push -u origin reading01        # Push branch to GitLab
   

   Note: You may edit and commit changes to your branch as many times as you wish. Just make sure all of your work goes in the appropriate branch and then perform a git push when you are done.

4. When you are ready for your final submission, you need to create a merge request via the GitLab interface:

   • First, go to your repository's Branches page and then press the Merge Request button for the appropriate branch:

     

   • Next, click on the "Change branches" link so you can set the Target branch to your own repository (rather than the class repository).

     

     Failure to select your own repository will lead to you unintentionally sharing your answers to the class, so please make sure you select your repository and not the class one.

   • Finally, assign the merge request to the instructor and submit the merge request.

     

   Every commit on GitLab will automatically submit your quiz or code to dredd and the results of each run is displayed in the merge request as a Pipeline task. To view the results of the submission, click on the Pipeline number and then the test button. You should then be able to see the results of the automated test, which should look something like this:

   

Once you have made the merge request, the instructor can verify your work and provide feedback via the discussion form inside the merge request. If necessary, you can update your submission by simply commit and pushing to the appropriate branch; the merge request will automatically be updated to match your latest work.

When all work is graded, the instructor will merge your branch and close the merge request.

Note: Please do not merge your own merge request. This makes it more difficult for the instructor to keep track of what needs to be graded.