Git, and Working Like a Developer
The version control segment that does not stop at commit and push. You make a history on purpose, read it backwards to find when something changed, hit a merge conflict nobody warned you about, and then spend a whole module getting work back after you have destroyed it.
- trending_upBeginner
- schedule7h 47m
- menu_book12個のレッスン
- publicEnglish
- workspace_premiumBasic
ブリーフィング
You have written programs. They live in a folder, and the folder holds exactly one version: the last one you saved. That is where this segment starts. You will make a repository, commit to it deliberately rather than in a panic at the end of the day, and write messages that mean something to a stranger six months from now. You will read a history backwards to find the single commit that changed a number nobody meant to change. You will branch, and you will hit a merge conflict before anybody explains what one is, because that is when the markers in the file finally make sense. Then module 3, which is the reason this segment exists. You committed a key. You committed to the wrong branch. You lost an afternoon of work and the log does not show it. You pushed something wrong and other people already have it. Four recoveries, each one caused on purpose, each one with the exact output, and every destructive command shown with the thing that gets it back in the same lesson. No account anywhere is needed. The remote you push to is one you create yourself, on your own machine, in a folder next door. By the end you will not have memorised git. You will be able to say what state a repository is in, and get it out of that state, which is the actual job.
コースアウトライン · 4個のモジュール
lockアクセスで解放- 01 A History You Made on Purpose3個のレッスン·1h 23m
Git records what you tell it to record, when you tell it. It is not a backup that runs in the background. Everything good about a history comes from somebody deciding where one commit ends and the…
- 02 Branches, and the Merge That Stops Halfway3個のレッスン·1h 52m
Branching is cheap and merging is not frightening. What is frightening is the first time git stops in the middle of a merge and leaves a file full of chevrons, and that happens to you in 2.2 with no…
- 03 The Four Recoveries4個のレッスン·3h 15m
You are going to work in repositories where other people's work lives. Every destructive command in this module is shown with the thing that gets it back, in the same lesson, because a command you…
- 04 Working Like a Developer2個のレッスン·1h 17m
The commands stop being the hard part after module 3. What is left is the part that gets you invited back: small changes, honest messages, and a repository that explains itself.
よくある質問
- Git, and Working Like a Developerでは何を学べますか?
- The version control segment that does not stop at commit and push. You make a history on purpose, read it backwards to find when something changed, hit a merge conflict nobody warned you about, and then spend a whole module getting work back after you have destroyed it.
- 事前の経験が必要ですか?
- いいえ — Git, and Working Like a Developerは基礎から始まり、初心者に適しています。
- Git, and Working Like a Developerはどのくらいの時間がかかりますか?
- Git, and Working Like a Developerには4個のモジュールと12個のレッスンが含まれています。自分のペースで学習できます。
- アクセスするにはどうすればよいですか?
- Git, and Working Like a Developerは任意の有料サブスクリプションに含まれています。