← Back to selected work
04 / CASE STUDY · PYTHON · DATA TOOLING

Exampulse.

A closer look at exam readiness.

Exampulse status sync and exam-readiness reports shown in two terminal windows using demo dataDEMO DATA
Actual Exampulse terminal capture · demo data
OVERVIEW

A Python command-line tool connecting wearable recovery metrics with exam schedules for personal, time-aware analysis.

MY ROLE

Personal software project · Python integration, data modeling, CLI experience, and test-focused analysis.

STATUS

Working local CLI · No hosted dashboard

TECH STACK
PythonWHOOP APIOAuthSQLModelSQLitepytest
01 — CONTEXT

The problem

Wearable data and exam schedules sit in different places, making it hard to inspect personal recovery and stress patterns around demanding days.

02 — APPROACH

The system

A Python CLI syncs WHOOP data via OAuth/API or imports official exports, stores records locally in SQLite, and generates readiness reports relative to a personal 14-day baseline.

ArchitectureSimplified system flow

WHOOP API / Exports

OAuth · Import

Python CLI

Sync · Commands

Local Analysis

14-day baseline

Connected from Local Analysis

Reports / Output

Terminal reports

SQLite

Local storage

03 — IMPLEMENTATION

Engineering highlights

  1. Excluded the target exam night from its own baseline to avoid contaminating comparisons.
  2. Implemented resilient ingestion and missing-data handling without inventing unavailable measurements.
  3. Designed local-first storage, idempotent import behavior, and privacy-conscious diagnostics.
  4. Added focused tests across API integration, time handling, analysis, reports, and error cases.
04 — REALITY CHECK

Scope & transparency

Readiness scores are personal exploratory indicators, not a validated medical or academic performance model. Some WHOOP streams may be unavailable; fine-grained heart-rate analysis requires separately supplied data. No public deployment or package-registry release was verified.

NEXT CASE STUDYRoomify