StackShadeStackShade Library
All courses
DevOps

DevOps & Git

Git mastery, Linux, CI/CD pipelines, Docker, Kubernetes, cloud infrastructure and observability — the full path your code travels from laptop to users, with hands-on labs at every step.

Intermediate
8 weeks
8 modules · 42 lessons
STACKSHADE / COURSE
DevOps

DevOps & Git

LEARNER OUTCOMES

What you should be able to do

  • Recover from any Git disaster with reflog-level confidence
  • Build CI/CD pipelines that test, build and deploy automatically
  • Containerize anything and orchestrate it on Kubernetes
  • Observe production with logs, metrics, traces and SLOs
TOPIC FORMAT

Every topic has two modes

Read — deep article with diagrams, artifacts and retrieval.

Present — focused deck with notes, pointer, timer and fullscreen.

Review — spaced review queue with due dates and recall ratings.

Focus — Pomodoro sessions, daily goals and a persistent scratchpad.

Loading progress…

Read → predict → inspect → retrieve. Your progress stays on this device.

0%
Loading study desk…
STUDY LOOP

Designed around learning, not scrolling

Each topic now has the full loop: article, visual explanation, artifact, retrieval and a recordable presentation.

Retrieval

Recall before revealing. The attempt is part of the learning action.

Spacing

Return at increasing intervals instead of rereading everything immediately.

Generation

Predict the next state or answer before seeing the worked version.

Dual coding

Pair compact prose with diagrams, traces, tables and motion.

Feynman

Teach the idea back in plain language to expose missing links.

Interleaving

Contrast nearby problem types so recognition becomes more useful.

CURRICULUM

Pick a topic

Git internals: blobs, trees, commits — the object graph
Video14 min
ReadDeck
Branching strategies: trunk-based vs GitFlow
Video12 min
ReadDeck
rebase -i, cherry-pick, reset (soft/mixed/hard)
Video16 min
ReadDeck
Interactive: disaster recovery with reflog
Interactive12 min
ReadDeck
Rescue lab: recover a 'lost' commit + fix a bad rebase
Practice30 min
ReadDeck
FEYNMAN PROMPT

Teach rebase vs merge as rewriting your diary vs stapling two diaries together.

ACTIVE RECALL
git reset --hard gone wrong — why is nothing ever lost?

reflog records every HEAD movement for ~90 days; find the pre-reset SHA and reset back to it.

Why never rebase shared/public branches?

Rebase rewrites commit hashes — teammates' clones diverge and every future merge duplicates/conflicts. Rebase local work only.

KEEP GOING

Another path next

View all

DSA Patterns

The 90-day pattern-based journey to Google-level DSA

Open

Computer Networks

How the Internet actually moves your data — visually

Open

Natural Language Processing

From raw text to Transformers, LLMs and production NLP systems

Open