Welcome to General Assembly SEI-CC-4
This will be your shared class repo! Guides, in-class labs and code samples, and other resources will live here.
- Class Repository Structure
- SEI GitHub Workflow
- Contact Information
- Course Information and Dates
- Immersive Graduation Requirements
/SEI-CC-4 /computer-science /projects /resources /work /w01 /d1 /01-topic /02-topic /03-topic /04-topic /hw-topic
DOM Manipulation & Events
Structuring a Browser App
|2||CSS: Flexbox, Grid & Responsive Design
JS: Callback functions, Classes, jQuery, this Keyword, Array Iterator Methods & Playing Audio
Project Deployment to GitHub Pages
|Full-stack Development||4||Client-Server: HTTP Communications & REST
NodeJS & ExpressJS Framework
MongoDB & MongooseJS ODM
|MEN-stack CRUD Application|
|5||Consuming & Producing APIs
Authentication using OAuth
Project Deployment to Heroku
|Second Language & Web Framework||7||Fundamentals of Python
Relational Databases & SQL
|Group Project: Full-stack Django Application|
|8||Django Web Framework
Project Deployment to Heroku
|Developing Single-page Apps||10||AJAX
|11||Client-side Routing (React)
Token-based Authentication (React)
Project Deployment to Heroku
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?source=header
- In another tab, browse to the GA class repo: https://git.generalassemb.ly/SEI-CC/SEI-CC-4
- 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-4
You can now
$ cd SEI-CC-4 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-4.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:
Handling 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
"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.
These coding challenges start with day 1 and will continue through week 8 (excluding project weeks).
Videos of Lessons
For your convenience, recordings of the lessons will be available to review at this YouTube channel.
|Global Instructor||Jim Clark||@Jim Clarkemail@example.com|
|Local Instructor - Austin||Shahzad Khan||@Shahzadfirstname.lastname@example.org|
|Local Instructor - Dallas||Daniel Scott||@Daniel Scottemail@example.com|
|Local Instructor - Santa Monica (LA)||Alex Rowland||@Alexander Rowlandfirstname.lastname@example.org|
|Local Instructor - San Fransisco||Brock Whitbread||Brock Whitbread-Coleemail@example.com|
- Course duration: Monday, July 22nd, 2019 - Monday, October 14th, 2019 (12 weeks, plus one-day extension due to holiday)
- September 2nd, 2019 (Labor Day)
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
- 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