Tôi có cần kinh nghiệm trước đó không?

Không — Git, and Working Like a Developer bắt đầu từ những kiến thức cơ bản và phù hợp cho người mới bắt đầu.

Git, and Working Like a Developer mất bao lâu?

Git, and Working Like a Developer bao gồm 4 mô-đun và 12 bài học. Bạn học theo tốc độ của riêng mình.

Làm cách nào để tôi có quyền truy cập?

Git, and Working Like a Developer được bao gồm trong bất kỳ gói đăng ký nào.

code programming

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 bài học
publicEnglish
workspace_premiumBasic

lock_open Bắt đầu học

Tóm tắt

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.

Nội dung khóa học · 4 mô-đun

lockMở khóa với quyền truy cập

01 A History You Made on Purpose
3 bài học·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 Halfway
3 bài học·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 Recoveries
4 bài học·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 Developer
2 bài học·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.

Các câu hỏi thường gặp

Tôi sẽ học gì trong 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.
Tôi có cần kinh nghiệm trước đó không?: Không — Git, and Working Like a Developer bắt đầu từ những kiến thức cơ bản và phù hợp cho người mới bắt đầu.
Git, and Working Like a Developer mất bao lâu?: Git, and Working Like a Developer bao gồm 4 mô-đun và 12 bài học. Bạn học theo tốc độ của riêng mình.
Làm cách nào để tôi có quyền truy cập?: Git, and Working Like a Developer được bao gồm trong bất kỳ gói đăng ký nào.

Thêm trong Lập trình

Beginner AI Without the Hype What the model is actually doing when it answers you, why that produces something that looks like thinking, why it invents citations, and the cost mechanic almost nobody explains: a chat resends the entire conversation on every single turn. You will do the arithmetic yourself.

Beginner First Program — Scratch for ages 5–9 Nine Scratch blocks, three sessions of about twenty-five minutes, and one small program a child of five to nine builds themselves. Written for the parent sitting beside them: what to click, what they will get stuck on, what to say when it goes wrong, and when to keep your hands off the mouse.

Beginner Binary, Hex and Data Units The topic that costs more marks than any other on the paper, taught by hand. Bits and bytes, binary and hex in all six directions, the 1000-versus-1024 trap, file sizes, transmission times, overflow, two's complement and character sets. Every module ends in a timed drill marked the way an examiner marks it.

Beginner Python From a White Sheet The exact sequence nine students have already walked, from a blank file to a program that asks questions, checks the answers and refuses bad input. No prior programming. No maths. You will break it repeatedly, on purpose.

Intermediate IGCSE and GCSE Computer Science — Theory That Actually Gets Marked The theory half of the paper, taught so it survives the exam room. The memory hierarchy and what actually happens at boot. Compilers, interpreters and assemblers, including the answer that sounds right and scores nothing. Databases from a spreadsheet up to keys and normalisation. DNS and the full path between pressing Enter and seeing the page. Systems software, and the ethical and legal section that is the easiest ten marks on the paper.

Intermediate Programming for the Exam — Python Answers That Score The programming half of the paper, taught at exam pitch. Pseudocode translated both ways, because the mark scheme is written in a notation nobody practises. Trace tables done column by column, including the ones with a loop and a condition inside it. Linear and binary search, bubble and insertion sort, what each costs and the comparison questions boards love. Validation against verification, and the boundary test data everybody forgets. Procedures against functions, and a systematic method for finding your own error with four minutes left.