Welcome to Coding Dojo's Python Cohort for August 2016
Probably the easiest workflow for you is to:
- Make sure you have git installed
- Create your own, free, GitHub account, if you don't have one already.
- Unless you have a particular affinity for the terminal, get a UI like SourceTree, thank me later (or buy me lunch).
- Fork this repository to your own GitHub account.
- When you log into your own github account, you should see the forked copy of this repo. Cone that forked copy located on your account onto your local machine
- Add an additional remote connection to the original repository (THIS one).
Intro to GitHub Flask MySQL Basic Routes [Full Friends](Currently Uploading...)
On your computer, you should see your cloned version of the repo. Open it up and create a new folder called 'LastnameFirstName', of course replacing it with your actual name. I'll show you all how to do this in class. Create two additional folders inside of it, 'Algorithms', and 'Assignments'.
Now, whenever you make changes inside your personal directory, you can first pull any updates from the main repository to your local machine, commit your changes to the local repo, push those commits to your forked version on GitHub, and finally make a pull request. This process will be video recorded and made available here shortly.
Every.Single.Damn.Day I want you to commit your class assignments so I can keep track your daily progress. Also after doing the morning algorithms during the week, type up your assignment into the example JS HTML page I've provided and submit that too. I'm going to be pissed if I don't see you making progress daily, even if it's a simple keystroke. You need to be programming every day to become a programmer.
At the Dojo, we only cover git for a portion of a day during Web Fundamentals (which most of you slept through =). When you graduate, you need to know how to use it comfortably and proficiently, otherwise you'll be the laughing stock of the town. You will be a version-control master by the end of this course because we'll use this repository to submit and review assignments. You can track the schedule and solutions in the Assignment Calendar as soon as I get it up. Likewise, the algorithm challenges you'll be expected to complete can be found in the Algorithms Calendar.
The second reason we're starting this is because that I like GitHub's social aspect, which will allow me to add comments into your code, have you correct your code, keep source control so you can see the evolution of your own progress, and again--get very familiar with pull requests, pushing, and merge conflict errors.
- SourceTree
- Markdown Cheatsheet The readme.md files are in markdown format
- More to come, trust me.