Backend Learning Tracker

Summary: a backend/database fundamentals project built around tracking learning themes, tasks, notes, and progress with production-style constraints.

Why I built it

I wanted a practical project that forced decisions around schemas, authentication, access rules, API boundaries, and query patterns. A tracker is simple enough to understand but still rich enough to model real product behavior.

What it does

The project organizes learning themes, tasks, notes, milestones, and review states. It is designed to practice API design and relational modeling rather than to become a polished SaaS product.

Tech stack

Node.js for API design, PostgreSQL/Supabase for data modeling, authentication, and role-based access patterns.

Key engineering decisions

I focused on a relational model that could answer useful questions: what is active, what is blocked, what changed recently, and which notes belong to which theme.

Problems I ran into

The main challenge was keeping the model small. It is easy to add too many tracking concepts before the core workflow is clear.

What I learned

Backend practice is better when it has product constraints. Authentication, permissions, schema design, and API responses are easier to learn when they support a real workflow.

What I would improve next

I would add a small audit trail, stricter validation, and tests around permission-sensitive routes.

Links

Project-specific repository and demo links are not public yet.