Class Indri

Evening Python Fullstack bootcamp. Oct 17 - Feb 27

Image generated with Dall-E

Staff:

Anthony Wallace, Instructor
- anthony@pdxcodeguild.com
Christian Alvarado, TA
- christian.a@pdxcodeguild.com

Capstones

Rough Timeline

Weeks 1, 2, 3, 4, 5: Python
Weeks 6, 7: HTML/CSS/Flask
Weeks 8, 9, 10, 11: Django
Weeks 12, 13, 14, 15: Javascript
Weeks 16, 17, 18: Capstone project

Scheduled Holidays (no class)

Oct 21 - Instructor Inservice (no class)
Nov 24 - Thanksgiving Day
Dec 26 - Christmas Day (Observed)
Jan 2 - New Years Day (Observed)

Assigned Labs:

JavaScript

Title	Due Date
Redo	20 JAN
Todo List	25 JAN
Weather API	01 FEB
Vue Redo	06 FEB

Django

Title	Due Date
Polls	28 DEC
Redo	30 DEC
Todo List	06 JAN
Chirp	13 JAN
Student API	09 FEB

HTML/CSS/Flask

Title	Due Date
Bio	07 DEC
Company Landing Page	10 DEC
Blog	12 DEC
Burrito Order Form	20 DEC
Flask Redo	24 DEC

Python

Title	Due Date
Unit Converter	02 NOV
Blackjack Advice	03 NOV
Pick6	08 NOV
Credit Card Validation	11 NOV
ROT13	15 NOV
Count Words	17 NOV
ARI	23 NOV
ATM	28 NOV
Dad Joke API	30 NOV
Quotes API	02 DEC

Class Folder Structure

class_indri
├── lecture_notes
├── lab_solutions
├── harry
│   ├── python
│   │   ├── notes
│   │   ├── turtle.py
│   │   ├── turtle_v2.py
│   │   └── mad_lib.py
│   ├── html_css
│   ├── django
│   └── javascript
├── ron
│   ├── python
│   ├── html_css
│   ├── django
│   └── javascript
└── hermione
    ├── python
    ├── html_css
    ├── django
    └── javascript

Submitting your work

Make sure all labs are located within class_indri/<YOUR_NAME>, where <YOUR_NAME> is your first name in all lowercase letters.

To emulate a more professional Git workflow, we're going to start creating new branches for each lab starting in the HTML/CSS section.

Creating a new branch:

Click to expand

git branch to check that you're on the main branch, use git checkout main to go to the main branch if needed.
git status to check if your local main branch is up to date with origin/main on Github.
git pull if needed to pull any recent changes to your local repository
Create a new branch and switch to it.
- Option 1:
  - git branch <YOUR_NAME-SECTION-LAB_NUMBER>
  - git checkout <YOUR_NAME-SECTION-LAB_NUMBER>
- Option 2:
  
  The -b flag can be used after the checkout command to combine these two steps:
  
  git checkout -b <YOUR_NAME-SECTION-LAB_NUMBER>
e.g. My branch for the "Lab 01 - Bio" in the HTML/CSS section would be named: anthony-htmlcss-lab01. The name can vary a bit from this example, but please keep the chosen formatting consistent from one lab to another.
git add <FILENAME> to add a specific file or git add . to add everything in the current dicrectory
git commit -m "your commit message" to commit your work
A remote branch will need to be created for each new local branch. Git will usually display the proper command to do this when a new branch is pushed for the first time.

The command is:

git push --set-upstream origin <BRANCH_NAME>

OR

git push -u origin <BRANCH_NAME>
After successfully pushing your new branch to Github, you should see the option to create a Pull Request for your branch on the main repo page.
If you don't see that message, you'll have to navigate to your new remote branch
Once you've navigated to your individual branch, you'll find the option to create a Pull Request in the "Contribute" dropdown.
Click the "Open Pull Request" button. Add a comment to your Pull Request like "Submitting Lab 00" and click "Create Pull request"

Updating a branch