Shadowing-Übung: How Git Works: Explained in 4 Minutes - Englisch Sprechen Lernen mit Video
Lektion wird erstellt...
1
Git can seem confusing at first, but understanding a few key concepts make it much clearer.
2
In this video, we'll walk through the basic Git command workflow and clear up some common misconceptions.
3
I'm San, co-author of best-selling system design interview books.
4
We explain complex system design concepts to animations.
5
Let's get started.
6
Before we dive into the commands, let's identify where a code is stored in Git.
7
The common assumption is that there are only two locations, but our code doesn't only exist on GitHub or our local machine.
8
There are forming locations where our code lives in Git.
9
The working directory, where we actively edit files locally, this is our playground.
10
The staging area, is a temporary holding spot for changes before committing.
11
The local repository.
12
This is where we store committed changes locally.
13
The remote repository, a server like GitHub for sharing and backing up code.
14
With these locations in mind, let's visualize where a code travels throughout its journey.
15
Most git command moves out between these four locations.
16
The first step is to git clone an existing repo, so you have a local version of the project to work on, complete with all its history.
17
With the repo cloned locally, let's look at where the code lives.
18
When you start working on a file, you're in the working directory.
19
This is your local development environment where you make changes to your code.
20
Now when you're ready to commit your changes, you use git add to stage a snapshot of those files in the staging area.
21
Think of this as a checkpoint where your code changes are gathered up and ready to be fired finalized.
22
The next step is to use git commit, which takes a snapshot of the staging area and saves it to your local repository.
23
This locks in those stage changes by creating a permanent record that you can refer back to, like a snapshot in time.
24
Your code doesn't just stay on your local machine.
25
When you're ready to share your progress with the team or back up your work, you use git push to send your commits to the remote repository.
26
This is often a shared server where your team can collaborate, like GitHub or Bitbucket.
27
Collaboration in Git is a two-way exchange.
28
To integrate your teammates' work, you use GitPull, which fetches changes from the remote repository and merges them into your local repository.
29
It combines two commands, GitFetch, which grabs the latest updates, and GitMerge, which integrates these updates with your work.
30
There are times when you need to switch contexts, perhaps to fix a bug on another branch.
31
This is where Git checkout or Git switch comes in.
32
It allows you to switch between different branches to work on specific features.
33
Git branching allows you to diverge from the main code base to develop a new feature without impacting the main code.
34
Some key concepts include creating a new branch with Git branch, switching between branches using Git switch,
35
merging branches together with Git merge or resolving merge conflicts when changes overlap.
36
Branching enables isolated development and collaboration workflows.
37
There are more nuance when merging or rebasing changes from others, or managing branches.
38
We have a dedicated video on merging and rebasing that we encourage you to watch.
39
Many developers use graphical Git tools like GitHub Desktop and SourceTree.
40
These tools provide visual interfaces and shortcuts for common commands.
41
They can help new users get started with Git more easily.
42
If you like our videos, you might like our system design newsletter as well.
43
It covers topics and trends in large-scale system design, trusted by 500,000 readers.
📺 Gleicher Kanal
C11
The Secret Sauce Behind NoSQL: LSM Tree
University StudentsBusiness English+1
C13
System Design Was HARD - Until You Knew the Trade-Offs
University StudentsBusiness English+1
C17
8 Most Important System Design Concepts You Should Know
University StudentsBusiness English+1
C13
Everything You Need to Know About DNS: Crash Course System Design #4
University StudentsBusiness English+1
C12
CAP Theorem Simplified
University StudentsBusiness English+1
C12
What Is REST API? Examples And How To Use It: Crash Course System Design #3
University StudentsBusiness English+1
C12
System Design: Why is Kafka Popular?
University StudentsBusiness English+1
C11
System Design: Why is Kafka fast?
University StudentsBusiness English+1
C12
10+ Key Memory & Storage Systems: Crash Course System Design #5
University StudentsWorking Adults
C24
What Is Redis Really About? Why Is It So Popular?
University StudentsBusiness English+1
C148
Kubernetes Explained in 6 Minutes | k8s Architecture
University StudentsBusiness English+1
C12
What Are Microservices Really All About? (And When Not To Use It)
University StudentsBusiness English+1
C13
How Does a URL Shortener Work?
University StudentsBusiness English+2
C1What is API Gateway?
University StudentsBusiness English+1
✨ Empfohlenes Video
B29
29 Sätze
Git Explained in 100 Seconds
American Accent, en-USUniversity Students+2
B21
269 Sätze
Design with Claude Code: The Designer’s Guide
University StudentsBusiness English+1
B21
103 Sätze
you will never ask about pointers again after watching this video
University StudentsBusiness English+1
B21
111 Sätze
how to edit vlogs
University StudentsBusiness English+1
B21
282 Sätze
What Stanford students actually use ChatGPT for
University StudentsBusiness English+1
B21
68 Sätze
GitHub Copilot now controls your command line...
University StudentsBusiness English+1
B258 Sätze
CI/CD Explained in 5 Minutes
University StudentsBusiness English+1
B22
200 Sätze
Give Me 15 Minutes. I'll Teach You 80% of Obsidian
University StudentsBusiness English+1
B22
159 Sätze
Electrical Engineering Simply Explained
University StudentsBusiness English+1
C11
78 Sätze
The easy way to keep your repos tidy.
University StudentsBusiness English+1
B21
22 Sätze
I'm an ex-Google interviewer. You're doing LeetCode wrong.
University StudentsBusiness English+2
B22
37 Sätze
How to Make a Mind Map - The Basics
University StudentsBusiness English+1
Über diese Lektion
Was ist die Shadowing-Technik?
Shadowing ist eine wissenschaftlich fundierte Sprachlerntechnik, die ursprünglich für die professionelle Dolmetscherausbildung entwickelt und durch den Polyglotten Dr. Alexander Arguelles populär gemacht wurde. Die Methode ist einfach aber wirkungsvoll: Du hörst englisches Audio von Muttersprachlern und wiederholst es sofort laut — wie ein Schatten, der dem Sprecher mit nur 1–2 Sekunden Verzögerung folgt. Anders als passives Hören oder Grammatikübungen zwingt Shadowing dein Gehirn und deine Mundmuskulatur, gleichzeitig echte Sprachmuster zu verarbeiten und zu reproduzieren. Studien zeigen, dass es Aussprachegenauigkeit, Intonation, Rhythmus, verbundene Sprache, Hörverständnis und Sprechflüssigkeit signifikant verbessert — was es zu einer der effektivsten Methoden für die IELTS Speaking-Vorbereitung und reale englische Kommunikation macht.