Welcome to General Assembly SEI-CC-6
This will be your shared class repo! Guides, in-class labs and code samples, and other resources will live here.
- Course Dates and Holidays
- Course Curriculum
- Instructional Team / Contact Info
- Link to Recorded Lessons
- Link to Deliverable Schedule
- Class Repository Structure
- Becoming Familiar With the SEI GitHub Workflow
- Immersive Graduation Requirements
Course Dates and Holidays
- Course duration: Wednesday, October 16th, 2019 - Friday, January 24th, 2020 (60 days - not including holidays)
- November 11th (Veterans Day)
- November 27th - 29th (Thanksgiving)
- December 23rd - January 1st (Winter Break)
- January 20th (Martin Luther King Day)
The following is an overall schedule and is subject to change.
|Fundamentals of Front-end Development||1
Basic Git Workflow
Setting up the Dev Environment
Fundamentals of HTML & CSS
CSS: Flexbox, Grid & Responsive Design
DOM Manipulation & Events
Structuring and Coding a Browser App
|3||JS: Callback functions, JS Classes
jQuery, this Keyword, Array Iterator Methods & Playing Audio
|4||Computer Science (CS) Topics
Project Deployment to GitHub Pages
|Client-Server: HTTP Communications
NodeJS & ExpressJS Framework
Intro to MongoDB & MongooseJS ODM
|MEN-stack CRUD Application|
|6||MongooseJS ODM (cont.)
Consuming & Producing APIs
Using a Hosted MongoDB
How to add features to a Web App
Authentication using OAuth
Begin Project 2
Project Deployment to Heroku
|Second Language & Web Framework||9||Fundamentals of Python
Relational Databases & SQL
Intro to Django Web Framework
|Group Project: Full-stack Django Application|
Begin Project 3
|Complete Group Project|
|11||Project Deployment to Heroku
Present Group Projects
|Developing Single-page Apps||12||AJAX
|13||Client-side Routing (React)
Token-based Authentication (React)
Begin Project 4
Project Deployment to Heroku
Instructional Team / Contact Info
|Global Instructor||Jim Clark||@Jim Clarkfirstname.lastname@example.org|
|Local Instructor - Austin||Shahzad Khan||@Shahzademail@example.com|
|Local Instructor - Dallas||Daniel Scott||@Daniel Scottfirstname.lastname@example.org|
|Local Instructor - Santa Monica (LA)||Alex Rowland||@Alexander Rowlandemail@example.com|
|Local Instructor - San Diego||Morgan Piersonfirstname.lastname@example.orgemail@example.com|
Link to Recorded Lessons
For your convenience, recordings of the lessons will be available to review at this YouTube channel.
Link to Deliverable Schedule
A Deliverable is an assignment that is required to be submitted as instructed to your instructors.
Unless otherwise stated, no deliverable will be accepted past its due date, which is typically 1 week from when the deliverable was assigned.
Graduation requires that 80% of deliverables be completed (working) and delivered on time.
Class Repo Structure
/SEI-CC-6 /computer-science /projects /resources /work /w01 /d1 /01-topic /02-topic /03-topic /04-topic /hw-topic
Becoming Familiar With the SEI GitHub Workflow
Forking (copying) the GA Class Repo to Your GitHub Account
You will have read-only access to the GA class repo. However, you most certainly will want to be able to make changes (e.g., add notes, save code exercises, etc). These changes will be saved to your own personal copy of GA's Student repo - known as a fork. To get this fork do the following:
- Make sure that you're logged in to your GA Enterprise GitHub account. If you have not signed up yet, here's the link to do so: https://git.generalassemb.ly/join
- In another tab, browse to the GA class repo: https://git.generalassemb.ly/SEI-CC/SEI-CC-6
- In the top-right corner of the page, click the
Forkbutton. SEI-CC Now you will have a copy of the repo in your Enterprise GitHub account!
Cloning Your Copy of the Repository Locally
Now that you have a copy of the class repo in your GitHub account, it's time to bring the contents of that repo onto your computer - this process is known as cloning and it only needs to be done once:
- On your Enterprise GitHub account, browse to your fork of the GitHub class repo and under the repository name click
Clone or download
- In the
Clone with HTTPSsection, click the clipboard to copy the URL for the repository.
- Open Terminal and navigate to your
~/codefolder - you may choose a different folder if you wish, however these instructions will assume you clone the repo into a folder named
- In Terminal, type
git cloneand follow it by pasting in the copied URL from the clipboard. The command should now look something like this:
$ git clone https://git.generalassemb.ly/YOUR-ENTERPRISE-GITHUB-USERNAME/SEI-CC/SEI-CC-6
You can now
$ cd SEI-CC-6 and check out your local copy of of the GA class repo!
Adding a git remote for the original GA class repo
A repo on your computer is called a local repo ("repo" is short for repository).
Repos on GitHub are called remote repos. Think of them as repos in the cloud.
When you cloned your fork of the repo, a "link" to the git remote was automatically created. You can check which remotes exist for a given local repo using this command:
$ git remote -v
Note that by convention, the remote that points to the GitHub repo it was cloned from is named origin.
However, in order to get the updates that the instructors push to the GA class repo, you will need to create another remote that points to GA's class repo that you forked:
$ git remote add upstream https://git.generalassemb.ly/SEI-CC/SEI-CC-6.git
Note that by convention, the remote that points to the original GitHub repo that was forked is named upstream.
$ git remote -v again will show that you now have two remotes:
origin (your fork of GA's class repo) and
upstream (GA's class repo).
Getting Changes Pushed by Your Instructors
Each day (maybe a few times a day), instructional materials may be pushed to the class repo by your instructors. You will want to "pull" these materials into your local repo (on your computer). Doing so will enable you to access "starter code", etc.
First, if you've made any changes within the repo locally, i.e., you've modified some starter code, you will need to commit those changes first:
$ git add -A $ git commit -m "Add amazing work..."
With local changes committed, you can now fetch the updates from the Github class repo and merge them into your local repo (on your computer):
$ git pull upstream master
From time to time, you will want to "save" the commits you have made locally to your forked GitHub class repo (in the cloud). Doing so is a good idea to ensure your work is backed up to the cloud in case of computer failure:
$ git push origin master
The above Git/GitHub workflow is summarized by this diagram:
Git Merge Conflicts
A merge conflict occurs when git merges two commits that have modified the same region of code and can't figure out whose code to use. Thus, fixing merge conflicts requires that a developer manually update the code to what it should be and re-commit it to resolve the conflict, which will also finish git's merge process.
Git informs you which files have merge conflicts and will annotate your code to show you how your local code differs from the code being merged from the remote. An example of such annotation is below.
<<<<<<< HEAD // Local code is here ======= // Changes you are pulling are here >>>>>>> 75c37cea922afc56e7d686adba063b986013ca9f
Once you have resolved these merge conflicts by editing the code and removing the markers, you can
During group project merge conflicts will likely occur giving you an opportunity to learn more about them then.
"Nested" repos are never permitted. Therefore, if you have important code, such as your projects, that belongs in its own repo, be sure to put that code in folders outside of the class repo.
There are 30 required code challenges that will help you get the necessary practice of writing code, as well as teach you new methods and techniques.
Just as with the class repo, you will fork & clone the code challenges repo.
You should complete one code challenge per day during the first 30 days, excluding project weeks.
GA SEI Graduation Requirements
General Assembly's courses are pass/fail programs. We have certain requirements in order to be considered a graduate of the SEI program:
- No more than 3 days absent from class over the duration of the course (3 tardies equals 1 absence)
- Successful completion of four assigned projects
- Successful completion of 3 of 4 project assessment challenges
- If you fail any part of a project (the project requirements, or the project assessment challenge), you can resubmit that part once.
- No violation of GA's zero tolerance plagiarism policy.
- Participating in GA’s mid-course and end-of-course feedback surveys
- Complete 80% of assigned "deliverables"
When you complete our program with passing status, you unlock our alumni perks:
- Support from the Outcomes Team, including participation in the Meet & Greet event (with prospective employers).
- Receive a GA Letter of Completion (via email 1 week after graduation)
- Credits and discounts for other GA courses (check with Student Services for details).
- Access to our Alumni Community