Kickoff: Building a Brazilian Jiu-Jitsu Training Tracker

I'm starting a new project: a data-driven tracker for my Brazilian jiu-jitsu training. The idea is simple—collect the data I already have scattered across services, bring it into one place, and build tools to visualize, analyze, and learn from it.

Data sources

• Gym training history: scraped/ingested from my gym’s website to log when I trained and what sessions I attended.
• Weight: exported from my digital scale (Renpho) to track daily/weekly trends and fluctuations around training days.
• Nutrition: MyFitnessPal data for calories and macros to correlate with performance, recovery, and weight changes.

What I want to learn

• How training frequency and intensity line up with weight, sleep/recovery markers (proxied for now), and nutrition.
• Whether certain macro splits or calorie ranges correlate with better sessions or faster recovery.
• If there are patterns around plateaus, injuries, or PR weeks that I can spot earlier.

MVP scope

• Automated importers for: gym sessions, Renpho scale exports, and MyFitnessPal logs.
• A unified schema so days/sessions are first-class and easy to query.
• Simple dashboards: calendar of sessions, weight trends, and overlayed nutrition.

Architecture sketch

• Ingestion: small scripts to pull from each source (scrape/API/export), normalize, and store.
• Storage: start with a single database/table group (sessions, measurements, nutrition) and iterate.
• Analysis: lightweight notebooks/queries to test hypotheses, then promote useful ones to dashboards.

Stretch goals

• Session tagging (gi/no-gi, positional sparring, comp class) and basic RPE/notes.
• Alerts for interesting patterns (e.g., sudden weight drops, missed days, calorie gaps before hard sessions).
• Simple planning tools—suggested deloads, fueling targets, and session cadence based on data.

Privacy and portability

This is a personal project. Data stays under my control, with export/import kept simple. If I open-source parts of it, I’ll keep credentials and personal data out of the repo and document mock data flows.

Why this matters

I already track most of this—just not together. Combining it should make it easier to spot what’s working (and what isn’t) and help me train smarter, not just harder.

I’ll share progress updates as I build ingestion pipelines, the schema, and the first dashboards. If you’ve done something similar—or have ideas for useful metrics—I'd love to hear them.

Current weight trend

This tracker will help me correlate training intensity, nutrition timing, and recovery with sustainable weight loss while maintaining strength and performance on the mats.