App Development Vocabulary — Day 19: Repository
Yesterday's package needs somewhere to be developed. That's the repository.
Think of it as a project folder with a memory. Every change is recorded. Nothing is lost when you overwrite a file, because the earlier version is still in the history.
A repo is also the unit of sharing. Open source packages on npm and PyPI almost always point back to a public repo, usually on GitHub, where you can read the source and report bugs.
Two copies is normal. The local repo on your machine, the remote repo on GitHub or GitLab. You work locally and push changes to the remote when they're ready. Tomorrow covers the tool that makes that work.
Quick check: You delete a file from a repo by accident. Is it gone for good?
## SPOKEN LINES
  • Your first Monday on a new team, and nobody sends you the code. The only instruction is clone the repo. One folder shows up on your laptop, holding the whole app plus three years of changes.
  • - REPOSITORY
  • - A repository is the home folder of a project. It keeps the full history: every version, who changed what, and when.
  • - You can open a file the way it looked six months ago, see who wrote line 40 and why, and get everything back if your laptop dies.
  • - So a repository is where a project's code and its history live. Tomorrow: Git, the tool that writes that history.
## NEXT
Day 20: Git
0
0 comments
Joshua Payne
4
App Development Vocabulary — Day 19: Repository
CMD & Conquer
skool.com/cmdandconquer
Learn to run AI agents from the command line. No API costs, no dev team — just you and your terminal. In-house courses, private repos, live calls.
Leaderboard (30-day)
Powered by