Daily micro-tips for C#, SQL, performance, and scalable backend engineering.
Commits aren’t deleted — they’re detached. What actually happens Rebase rewrites history Old commits lose branch references They become unreachable, not gone Recovery git reflog git checkout <lost-commit-hash> Lesson If Git feels scary, you’re missing the mental model, not commands.
git restore . Why it mattersModern replacement for dangerous commands.
git log -S “methodName” Why it mattersFind when logic changed, not just files.
git blame file.cs Why it mattersContext beats guesswork.
git commit –amend Why it mattersClean history, no noise.
git log –oneline –graph –all Why it mattersInstant mental model of the repo.
git stash push -m “temp” file.cs Why it mattersCleaner context switching.
Huge repo? Clone only what you need. git clone –filter=blob:none <repo> Why this mattersMassive bandwidth and disk savings for CI and dev machines.
Never git reset on shared branches. git revert <commit-hash> Why this mattersCreates a safe inverse commit — teammates stay happy.
git pull = fetch + merge (implicit and risky). git fetch origin git rebase origin/main Why this mattersCleaner history, fewer merge commits, easier reviews.
Ever committed secrets or junk? git reset –soft HEAD~1 What happensCommit undone, changes preserved, history clean.
No conflicts, code wrong. Why it happensAutomerge overwrote assumptions. Why it mattersSilent regressions. Vital fix Review diffs before pull.
Commits fine, logic broken. Why it happensReverts without context. Why it mattersDebugging history useless. Vital fix Prefer revert commits with explanations.
Clone gets slower. Why it happensLarge files tracked forever. Why it mattersCI pipelines slow down. Smart fixUse Git LFS early.
No conflicts, still bugs. Why it happensSemantic conflicts are invisible. Why it mattersProduction errors. Smart fixRebase for logic clarity.
Errors reach main branch. Why it happensNo automated checks. Why it mattersBugs spread fast. Smart fixUse pre-commit hooks.
Too many “fix” commits. Why it happensNo commit hygiene. Why it mattersCode reviews slow down. Smart fixSquash logically related commits.
Same files, same pain. WhyLong-lived branches. TipMerge often, keep branches short.
Fear of losing work. WhyRebase misunderstood. TipUse rebase on local branches only.
Dead branches pile up. WhyNo cleanup policy. TipAutomate stale branch deletion.
Commits exist, meaning lost. WhyOverloaded commit messages. TipOne intent per commit.
Same files, same pain. WhyUnclear ownership boundaries. TipDefine ownership per directory.
Clone times increase. WhyLarge binary history. TipMigrate binaries to Git LFS early.
Commits exist, context is gone. WhyMessages describe actions, not intent. TipExplain why, not what.
Small changes cause big conflicts. WhyNo branch discipline. TipShort-lived feature branches.
Merges become painful. WhyBranches drift far from main. Tip Rebase or merge frequently.
History exists, context is lost. WhyCommit messages lack intent. Tip Write commits explaining why, not what.
Every merge hurts. WhyUnstable file ownership. Tip Define code ownership early.
Commits exist, meaning is lost. WhyMixed-purpose commits. Tip One intent per commit.
Everyone touched everything. WhyFormatting commits pollute history. Fix Separate formatting-only commits.