Image provided by @nico_photos
At time of writing, I’ve just finished the second year of my CompSci degree and am taking a placement year in industry. Two years ago, I had absolutely no programming experience and I’m sure there are other people in a similar situation.
Here’s what I wish somebody had told me…
If your course is structured anything like mine, you might not encounter Git at all until second year. Given that it’s such a fundamental part of this field, this is unacceptable. GitHub will become your public technical profile, a way to share your work with others and an access point like a portfolio you can show to employers.
GitHub is used for version control. Whenever you make a significant change to your code, you upload the change (called a ‘commit’), and the project (‘repository’) can be rebuilt any number of times using this commit history. For example, my personal website has a repository, and you can see a detailed list of the commit history.
Assuming you’ve got a GitHub account set up and project in mind, getting started with version control is simple.
Through the GitHub site, create a new repository. There will be an option to initialise the project with a
README.md, which is good to check. That will create an empty Markdown document that will be displayed on the repositories page to share important information with people viewing it.
With this created, you’ll be presented with a page like this, albeit much more empty. There will be a button in the corner,
Clone or Download, and when you click it you’ll be given a link:
Get a copy of this!
You’ll need to open up a command line -
cmd.exe on Windows, or
Terminal on Mac. This will by default open in your root drive (Windows uses
C:\ by default) and you can use basic commands to navigate to where you want to store your repositories. I’ve put a command cheatsheet below, feel free to refer to this if you’re unsure
mkdir documents/repositories cd documents/repositories
…clone a local copy of your repository..
git clone https://github.com/your-github-username/your-repository-name.git
… and navigate into your repository
That’s the setup for local development sorted! You can do this from any machine and get a copy of your repository to use anywhere. You can create your project in this directory and start to fill in content.
When you have something you want to upload - this can just be setting up the default project, for example - go to the next steps.
With your command line set up as before and already in the correct directory, you’re good to make your first commit
Check what you’re about to upload. Run the following command which will show you what files you’re about to commit
N.B here a
> denotes a response from the terminal
git status > On branch github-blog-post > Changes not staged for commit: > (use "git add <file>..." to update what will be committed) > (use "git checkout -- <file>..." to discard changes in working directory) > modified: _layouts/post.html > modified: collections/_blog-posts/01-github-for-beginners.md > no changes added to commit (use "git add" and/or "git commit -a")
This response is telling me that, at time of writing, I’ve modified two documents in my repository - both related to the blog post I’m writing at the moment.
Stage these changes for commit - this is where you select which changes to include in the commit
git add collections/_blog-posts/01-github-for-beginners.md # --- # Alternatively, to add all changed files... # --- git add -A # --- # And to add all modified or deleted files, but NOT new files... # --- git add -u
Create a commit for these changes. Give this a message with the
git commit -m 'Added making a commit tutorial' > git[github-blog-post 5b36022] Added making a commit tutorial > 2 files changed, 69 insertions(+), 6 deletions(-)
And push this to your repository:
git push > Enumerating objects: 13, done. > Counting objects: 100% (13/13), done. > Delta compression using up to 8 threads > Compressing objects: 100% (7/7), done. > Writing objects: 100% (7/7), 4.03 KiB | 4.03 MiB/s, done. > Total 7 (delta 2), reused 0 (delta 0) > remote: Resolving deltas: 100% (2/2), completed with 2 local objects. > To https://github.com/delete-44/website.git > dc92a21..5b36022 github-blog-post -> github-blog-post
Now if you visit your repository on GitHub,
https://github.com/your-github-username/your-repository-name, you’ll see your changes published there. Now you’ll also be able to visit the
commits tab to see a history of your changes, and view an individual commit to see the diff report.
Explore as much as you want to - this will become very familiar very quickly, so don’t worry if the command line stuff seems daunting at first.
There are of course more advanced steps with version control that are designed to give you an efficient and thoroughly tested workflow that you’re welcome to research - branches & pull requests are a good start.
cd: Change directory, this is used for traversing your storage in the command line. For example,
will navigate to, if the source is found, the repos folder in your documents.
can be used to navigate up a path level, for example if you’re already in
repos and want to return to
-Aas options to add all changed files
-moption to add a message to this commit
Thats the tutorial part of this post covered - from here on out it’s just a few notes I feel would be useful to anyone starting a programming course.
You’re interested in making mobile apps? Do it. You’re interested in making games? Start. If theres something that makes you genuinely excited and passionate about programming, exploit it. You’re going to work on a lot of boring projects in your life, don’t let whatever inspired you to study this in the first place get squashed by them.
To this end, don’t limit yourself to the boring projects at all. I play Dungeons & Dragons
(shocking), so I made a simple C# program that rolled dice for me in case I ever forgot mine. I learned VBA and made a faux procedurally-generated mapmaker in Excel.
It doesn’t matter how seemingly small or insignificant these projects seem, if it keeps you engaged and eager to learn new skills, it’s worth it.
But I’m barely a first year! I know how to make a terminal say my name and that’s about it, I hear you cry. And to that I say get on Google and get on tutorials. Before my placement started I taught myself the basics of Ruby on Rails using this wonderful tutorial.
My best recommendation is to decide on a language or framework you’re interested in. This could be by:
You have complete freedom over what you choose to study outside of your course. Take advantage of this time!
Hackathon: An organised event (check with any computing societies at your university, or the MLH website to see when) that, in my experience, are dedicated 12-hour sessions of programming around a given theme
Struggling to find time to work on your own projects? Take part in events organised for people like you. Hackathons are a great learning experience and can be a lot of fun. In my experience they…
If you don’t have any projects in mind, turn up anyway - there’s typically a prompt to inspire you.