Git on Work You Can Explain

Recovering Git History and Lost Code

Wed, 19 Aug 2026 00:00:00 -0500

Git may be able to recover code that disappeared from your current branch, but recovery begins with inspection. A reflog records local movements of references such as HEAD; it does not guarantee that every file or commit still exists, and it is not a substitute for a remote or tested backup.

The safe pattern is: protect the repository, inspect history, create a recovery reference, compare the candidate, and restore only after verification.

Set Up Git, SSH, and Course Toolchains on Linux

Thu, 30 Jul 2026 00:00:00 -0500

Set up only the environment one course requires. Record the supported Linux distribution, exact tools and versions, repository host, authentication method, project location, and verification command. Then install through the distribution’s supported package path and prove the environment with a disposable practice project.

Do not install every language, copy a classmate’s dotfiles, or create an SSH key before checking whether the course uses SSH at all.

Write the requirement sheet

Ask the syllabus, instructor, or official course environment:

Set Up Git, SSH, and Course Toolchains on macOS

Thu, 30 Jul 2026 00:00:00 -0500

Build one course environment, not a collection of every developer tool you may use in college. Start with current course instructions, verify the Apple developer base, configure Git identity deliberately, add SSH only when the remote service or course requires it, and isolate project dependencies through the course’s documented method.

Keep passwords, private SSH keys, access tokens, recovery codes, and private repository addresses out of setup notes and screenshots.

If Apple’s developer base has not been inspected, first install or verify Xcode Command Line Tools. Do not let an automatic developer-tools prompt become an unexplained side effect of the Git setup.

Use Git Worktrees for Parallel AI Agents

Sun, 26 Jul 2026 00:00:00 -0500

Use Git worktrees for parallel AI agents only when the tasks can be separated clearly. Create one branch and linked working directory per task, assign exclusive files or responsibilities, inspect each result independently, and integrate one commit at a time.

Worktrees reduce interference between working directories. They do not make overlapping designs, stale assumptions, or conflicting recommendations safe.

Understand what a worktree isolates

The official git worktree documentation states that one repository can support multiple working trees and have more than one branch checked out at a time.

`git status` and `git diff`: Your Safety Instruments

Fri, 24 Jul 2026 00:00:00 -0500

Run git status and git diff before committing, switching tasks, or accepting an AI-generated edit. They answer different questions: status summarizes file states; diff shows the content changes behind those states.

Read status as an inventory

The official git status documentation states that it reports differences between HEAD and the index, between the index and working tree, and untracked files not excluded by ignore rules.

In practical terms:

untracked means the file is present but not in Git’s index;
modified, not staged means the working copy differs from the index;
staged means the index contains a change proposed for the next commit; and
clean means Git sees no tracked or untracked change to report under the current rules.

Clean does not mean correct, tested, backed up, or pushed.

A Beginner’s First Programming Workflow

Fri, 24 Jul 2026 00:00:00 -0500

Use one repeatable loop for beginner programming work: understand the task, plan one small change, change the code, run it, test the expected behavior, and create the checkpoint required by the project. A Git project can use a commit; another course may require a working-log entry, saved version, or submission. Each step produces evidence for the next.

The loop prevents a vague assignment from becoming a large, unexplained edit.

1. Understand the task

Before editing, state:

GitHub Is More Than Online Storage

Fri, 24 Jul 2026 00:00:00 -0500

GitHub can store a remote copy of a Git repository, but its larger role is collaboration around that repository. It adds access controls, issues, pull requests, review, automation, releases, and project presentation.

Separate Git from GitHub

Git records repository history locally. GitHub hosts repositories and services around them. A remote is a named location used to exchange repository data; it is not the only valid copy and does not replace a tested backup.

How to Make a Useful Commit

Fri, 24 Jul 2026 00:00:00 -0500

A useful commit is a small, understandable checkpoint. It contains one logical change, excludes unrelated files and secrets, records a descriptive message, and follows relevant verification.

Define the change before staging

State the outcome in one sentence:

Add input validation for an empty student name.

If the sentence requires “and” to join unrelated outcomes, consider separate commits. A single logical change may touch code, tests, and documentation when they jointly implement one outcome.

Source Files and Generated Files Are Not the Same

Fri, 24 Jul 2026 00:00:00 -0500

A project folder can contain files that look equally important but have very different roles. The Markdown document you edit is not the same kind of artifact as the PDF exported from it. Raw measurements are not the same as a chart generated from those measurements.

The practical rule is simple: protect what you cannot reliably recreate, and document how to recreate everything else. This requires more judgment than sorting files by extension.

Stop Naming Files “Final-Final-2”

Fri, 24 Jul 2026 00:00:00 -0500

essay-final-final-2.docx does not tell you which copy is editable, which one a classmate reviewed, or which one you submitted. It records a sequence of uncertain decisions in a place that should identify the file.

Use a stable descriptive name. Add a sortable date or meaningful state only when it answers a real retrieval question. Keep one clear editable source, and use document version history or Git when the work needs actual change history.

Sync, Git, and Backup Solve Different Problems

Fri, 24 Jul 2026 00:00:00 -0500

Sync, Git, and backup can all create additional copies of data, but they solve different problems. Sync keeps selected files available across locations. Git records deliberate versions of a project. Backup preserves recoverable copies for loss or damage. A reliable student system assigns each layer a specific job.

Why one extra copy is not enough

Suppose a student keeps a programming project in a synchronized folder. The folder appears on a laptop and in a cloud service. This helps when the student moves between devices. It does not answer every recovery question:

The Small CLI Toolkit Worth Learning

Fri, 24 Jul 2026 00:00:00 -0500

You do not need dozens of command-line tools. Recognize a small set, then learn each one when a real course or project creates the need.

Git, SSH, curl, ripgrep, find, jq, and GitHub CLI cover seven useful roles: version history, remote access, data transfer, content search, file search, JSON processing, and GitHub workflows. They are a learning queue, not an installation checklist.

Choose a problem before a tool

For each proposed tool, answer:

Use Obsidian, Notion, Git, and Office Without Duplicating Everything

Fri, 24 Jul 2026 00:00:00 -0500

Using several tools is not automatically a problem. Duplication becomes a problem when two copies both appear authoritative. Assign each tool one clear responsibility, keep one canonical source for each artifact, and use links or short summaries across boundaries.

Divide by responsibility

A useful default is:

Tool	Canonical responsibility
Obsidian	Personal concepts, learning notes, and private connections
Notion	Shared coordination, structured group state, and discussion
Git	Technical source, tests, configuration, and project documentation
Office	Required rich-format collaboration and deliverables

These are defaults, not ownership claims by a product. A course requirement, institutional policy, accessibility need, or project constraint can change the assignment.

What Git Is Actually Tracking

Fri, 24 Jul 2026 00:00:00 -0500

Git is a version-control tool that records selected project snapshots locally. It appears in this path because a course or project may use that history to inspect and explain changes. Git does not watch every file on the computer or save every keystroke. In one repository, Git compares the working tree, the staging area, and committed snapshots. You decide which file content enters the proposed next snapshot and when that snapshot becomes history.

Why Plain Text Works So Well with Git, CLI Tools, and AI

Fri, 24 Jul 2026 00:00:00 -0500

Git, command-line tools, and AI systems perform different jobs, but plain text gives them a common interface. Visible characters and lines can be searched, compared, transformed, copied into a prompt, and reviewed after an edit.

This is a practical advantage, not a claim that text is always best. Text works well when the important information can be represented clearly without hiding its structure inside one application.

Text exposes the content

In a Markdown file, the stored content is readable:

Your First Merge Conflict Should Be Deliberate

Fri, 24 Jul 2026 00:00:00 -0500

A merge conflict is Git asking a person to decide how overlapping changes should combine. Practice once in a disposable repository, with a clean working tree, before deadlines or team work make the decision stressful.

Create a controlled conflict

Use a new practice repository with no important files. Commands assume a recent Git installation and a default branch named main; adjust the branch name only if your repository uses another one.