Why This Matters
Before writing a single line of backend code,
your environment setup determines how professional
and secure your workflow will be.
Setting Up .gitignore
A .gitignore tells Git which files to never track.
This is critical because you never want to push sensitive
files like .env (which contains secrets and API keys)
to a public GitHub repo.
My .gitignore for this Python/FastAPI project:
__pycache__/
*.pyc
.env
venv/
.vscode/
*.log
Branching Strategy
Instead of committing everything directly to main,
I created a develop branch:
git checkout -b develop
This is how real teams work:
- main > stable, production-ready code
- develop > active development
- feature branches > individual features
Never push broken code to main.
The Commit Hash
Every commit in Git has a unique hash :
a fingerprint for that exact state of your code.
git log --oneline -1
// 381fc57 - Day 03 setup
This means you can always roll back to any
point in your project history.
Lessons Learned
A clean Git setup isn't optional :
it's the difference between an amateur project
and a professional one. Protect your secrets,
branch your work, commit with intention.
Day 3 done. 27 more to go.
Top comments (0)