hackhaton-space-stackHackhaton Space Stack
AcademyBuilder
Get Started
All terms
The Basics
  • Stack
  • Frontend & Backend
  • CLI
  • Monorepo
  • Server
  • Localhost
How AI Works
  • Context Window
  • Hallucination
  • Token
  • Prompt Caching
  • Session
  • Compaction
  • Embedding
  • Vector Database
  • RAG
  • Fine-tuning
  • Temperature
  • Inference
  • Reasoning
  • Multimodal
Building With AI
  • Agent
  • MCP
  • System Prompt
  • Skill
  • CLAUDE.md
  • Slash Command
  • Harness
  • Computer Use
  • Agents SDK
  • Voice Agents
  • OAuth
  • Vibe Coding
  • Permission Scope
  • Tool Calling
  • Prompt Injection
  • Eval
  • Guardrails
  • Sandbox
  • Progressive Disclosure
Code & Collaboration
  • Git
  • Commit
  • Branch
  • GitHub
  • Pull Request
  • Open Source
  • Markdown
  • Dependency
  • Merge
  • Fork
APIs & Connections
  • API
  • Auth
  • Database
  • ORM
  • SDK
  • Webhook
  • Endpoint
  • REST
  • HTTP Methods
  • Env File
  • Schema
  • JSON
  • YAML
  • Secret
  • Rate Limit
  • CORS
  • Cookie
  • Encryption
Shipping & Running
  • Deploy
  • Headless
  • Cron
  • DNS
  • CDN
  • Object Storage
  • Serverless
  • Edge
  • Worker
  • Runtime
  • Process
  • Daemon
  • Queue
  • Job
  • State
  • Cache
  • SSH
  • Build
  • Staging
  • Rollback
  • Docker
  • Feature Flag
  • Test
  • CI/CD
  • The Cloud
Debugging & Errors
  • Trace
  • Type Error
  • Stack Trace
  • Log
  • Bug
  • Patch
  • Latency
How Developers Think
  • DRY
  • YAGNI
  • KISS
  • Refactoring
  • Technical Debt
  • Async
← All terms

Type-safe, modern TypeScript scaffolding for full-stack web development

ThreadsGitHub

Info

  • Academy
  • Docs

Legal

  • Terms of Service
  • Privacy Policy

© 2026 Dzulhelmy Nazri

Code & Collaboration

$definegit--plain-english

Git

TLDRSave points for your code.

Git is a numbered sketchbook. You never scribble over last night's page. You turn to a new one.

The book lives on your laptop. Every commit is a full page: every file, as it was, plus a caption. A branch is a second book clipped to the first — same opening pages, different mess. GitHub is the studio shelf. You park the book there so another laptop, a teammate, or an agent can open the same pages.

You do not need to "know Git." You need three habits.

Save the page before you wreck it

Hackathon pace plus an agent — MCP, the plugin, whatever is driving the CLI — will break things. That's the job. Take a page when login works. Take another before you "just rewrite auth." If the rewrite is a crime scene, you flip back. The working page is still there.

npx create-hackhaton-space-stack@latest hands you a repo. The first useful move is not another pass through the builder. It is a commit while the generated app still boots.

Don't rip pages other people already copied

History you already pushed is a shared wall. Rewriting it is tearing sheets out of someone else's book. Merge forward. Don't pretend Friday never happened.

Git tracks lines, not vibes. It knows what you added, what you deleted, and when. "It ran before lunch" becomes a flip through pages, not a guess.

The book also travels. Clone it on a second machine and the whole numbered stack comes with you. That is why the scaffold is a repo, not a zip you email yourself.

What this unlocks

Fearless edits. The sketchbook is why you can let an agent try the dumb idea.

Keep turning pages. The book outlives the bad hour.

Related

  • Commit
  • Branch
  • GitHub
  • Merge
PrevProgressive Disclosure

Code & Collaboration

NextCommit