Listen Now

"Do you have any advice on finding a job as a developer?" Many people have asked me that question, but I can’t give a proper answer because I have never been hired as a developer before. I'm horribly equipped to answer questions about finding a job. But Chris Lienert is great at it. Chris has experience hiring and building teams of excellent developers. And he has lots of golden nuggets to share with you in this episode.

Video:https://youtu.be/xlQIABDgTOs Article: https://zellwk.com/blog/gitignore

Video: https://youtu.be/grKh2Sl35bE Article: https://zellwk.com/blog/what-not-to-save-into-a-git-repo

I will share things on my screen in this episode, so the best way to consume this episode is through text or video. Video: https://youtu.be/59OgWy4BO90 Text: https://zellwk.com/blog/git-tags

This episode shows you: How to merge a pull request How to review a pull request How to editing a pull request I will share things on my screen in this episode, so the best way to consume this episode is through text or video. Video: https://youtu.be/UpBpb0j7IKA Text: https://zellwk.com/blog/edit-pull-request

This episode shows you What is a pull request How to submit a pull request if you have write access How to submit a pull request if you don't have write access I will share things on my screen in this episode, so the best way to consume this episode is through text or video. Video: https://youtu.be/ Text: https://zellwk.com/blog/

This episode shows you When to use Git Stash How to create a stash How to apply a stash I will share things on my screen in this episode, so the best way to consume this episode is through text or video. Video: https://youtu.be/pmpGsPDPLrI Text: https://zellwk.com/blog/git-stash

This episode shows you Why use semantic versioning What is a patch versions What is a minor version What is a major version How to handle pre-releases I will share things on my screen in this episode, so the best way to consume this episode is through text or video. Video: https://youtu.be/rTZ35Subk9U Text: https://zellwk.com/blog/semantic-versioning

This episode shows you What is Git Flow: 00:00 Creating a Git Flow: 00:40 Starting a feature: 01:50 Starting a release: 07:00 Starting a hotfix: 12:35 Do you need Git Flow: 16:20 I will share things on my screen in this episode, so the best way to consume this episode is through text or video. Video: https://youtu.be/AlcKgpedAO0 Text: https://zellwk.com/blog/git-flow

The best way to consume this episode is through video because I share things on my screen. Video link: https://youtu.be/yARRMa9zssw Text version: https://zellwk.com/blog/git-branch This episode shows you What is a branch How to create a branch Why create a development branch How to code on a new branch How to push branches into the remote How to switch branches How to merge branches How to delete a branch

The best way to consume this episode is through video because I share things on my screen. Video link: https://youtu.be/qLFj3H0j998 Text version: https://zellwk.com/blog/resolving-git-conflicts This episode shows you: What is a Git Conflict How to produce a conflict How to resolve a conflict How to prevent conflicts from happening

The best way to consume this episode is through video because I share things on my screen. Video link: https://youtu.be/nsORVjJTkeI Text version: https://zellwk.com/blog/your-first-git-commit This episode shows you how to: Clone a project Switch between projects in your Git client Give a friend collaborator rights

When you make a change to a local repository, you can push a change to a Git remote. Likewise, when the remote gets changed, you can pull the changes back to your local repository. The best way to consume this episode is through video because I share things on my screen. Video link: https://youtu.be/nsORVjJTkeI Text version: https://zellwk.com/blog/your-first-git-commit This episodes shows you: How to change the remote repository How to fetch changes How to pull changes to your local repository

The best way to consume this episode is through video because I share things on my screen. Video link: https://youtu.be/dqRN8IXvsOg Text version: https://zellwk.com/blog/pushing-to-a-git-remote This episode talks about: The differences between Git services How to create a repository on Github How to link your local repository to the remote repository How to push to the remote repository

The best way to consume this episode is through video because I share things on my screen. Video link: https://youtu.be/nsORVjJTkeI Text version: https://zellwk.com/blog/your-first-git-commit The staging area If you open up Fork from where we left off previously, you'll see the project screen. If you click on changes, the screen will split into two parts. On the left of the screen, you'll see a section that says unstaged files. Below this section, you'll see another another section that says staged files. To the right, you'll see a placeholder that shows Fork's icon. At the bottom, you'll see a few fields: A commit message field A description field An ammend checkbox A commit button This place is called the staging area. This is where you decide what files you want to save into Git. Staging a file Before you save anything, you need to make a change in the Git repository. Open up your Git project in a text editor like VS Code. Create a file called index.html and give it some HTML to start with. Once you save this file, you'll see this file in the staging area. It should appear in the unstaged files section of the staging area. An unstaged file is a file that has been changed since you last committed into the Git repository. If you want to commit a file (in this case, the index.html file), you can click on the file and click on stage. This file will be moved from the unstaged files section into the staged files section. When you have a file in the staged file section, what you're saying is you want to save that file when you make a commit. If you click on the file, you'll see the lines of code (in green) that will be saved into the repository. Creating a commit To create a commit, you write your commit message at the bottom right corner, then click the "create commit" button. Once you click on the commit button, the staged files will disappear from the staging area. This is because the files are saved; there are no more new changes for the file in the repository. Committing more than one file You can commit many files at the same time. To do so, you need to change many files. In this example, I added a CSS file and a JavaScript file to the repository. I also added code to the index.html file to point to the CSS and JavaScript files. If you go back into Fork now, you should see the folders and files that are changed. To commit all three files at once, you select the files and click the stage button. Then, you write your commit message and commit the files. Checking the Git History If you click on All Commits in the sidebar, you'll see the commits you have made so far. In some Git clients, this is called Git History. Exercise Try to make a few commits into your Git repository with Fork. In the next video, I'll show you how to push to a git remote and how to pull from a git remote.

The best way to consume this episode is through video because I share things on my screen. You can view the video at this Youtube link: https://youtu.be/0z2vRogzbMQ You can also read this as an article: https://zellwk.com/blog/setting-up-git What is Git? Imagine you're playing a game. In this game, you can create save points. When you die in the game, you will need to load your game and continue from your save point. If you didn't create a save point, you will start all the way at the beginning of the game again. That's not a fun experience, so its always a good idea to save your game. Git is like a save point system for your work. You can create save points. In Git we call each save point a commit. When you create a commit in Git, you can load your work from that commit. If you create five commits, you can load your work from any of these commits. That's what Git is for. We call it a version control system because you can save and load your work from any commit. Choosing a Git Client Many people teach you how to use Git with a command line, but that can be scary for beginners. We're going to throw away the command line and use applications to help you get started with Git. These applications are also known as Git clients. My favorite Git Client is Tower. It is extremely powerful. The only downside to Tower is it costs $55.20 each year. If you're new to programming, you might not want to start with Tower. You might want to try a free application instead. Here are some good free apps: Sourcetree GitKraken Fork Sourcetree is probably the best free app out there. It is good and has features on par with Tower. But Sourcetree can be buggy, and you might not be able to resolve the errors yourself. (I tried, and I couldn't). GitKraken is another popular app that many people like. I believe GitKraken is too fancy and focuses on the wrong things though. Fork looks clean and simple, and is pretty good to get started with. It's in beta right now, so its free, but you might need to pay for it later. I'm going to show you how to setup Fork.

I'm going to start a podcast. But why am I starting a podcast when I'm already doing video every Friday? I wanted to start a podcast before starting a video because podcasts seem to be way less intimidating compared to videos. But I also wanted to teach code, and podcasts wouldn't be a very good medium for it. Overtime, I realized that most of the videos I put out only contain audio, so you don't have to watch me on screen. That is true for the past 10-15 videos. It'll be boring if you watch nothing but me talk to you for 5-10 minutes. You can't do anything else. You need to have your Youtube tab or Youtube app open. I only realized that my content is suitable for podcasts when one of my students in Learn JavaScript brought it up to me. She asked why I didn't start a podcast instead. So I thought, why not do both of them at once? That's why I'm starting a podcast. Everything is still raw I don't even know whether the process I have to put this video into Itunes will work well. I'm testing things out. If this podcast works, you'll find a link to the podcast episode. Few more things The podcast will be called Fridays with Zell. This is the same name as the video you're watching every Friday. This also means the video won't change much. I will include a link to the podcast in the video description and I will also include a link from the podcast to the video for you to switch between modes easily. The only change is this: Sometimes I might create content that requires you to look at the screen. If I do, I'll tell you about it. Experimenting again! This episode is very raw. Things are all over the place now, and I don't have an idea whether this is going to work. But I want to let you know because things are changing. I'm sure that things will get polished overtime.