Sswetank.dev

active project

LeetCode API Explorer

A local-first project page for exploring API design, problem metadata, caching, and developer-friendly documentation.

Next.jsTypeScriptAPI design

Links

Demo/source links can be added later from Sanity.

Problem

Learning from API design is easier when the data can be inspected locally, queried quickly, and documented through real examples.

Outcome

A portfolio-ready case study shape for APIs, caching, and practical developer tooling.

System sketch

How this project moves.

active
01Problem
02Inputs
03Prototype
04Proof
05Writeup
06Next

Approach

  • Model problem metadata separately from transport details.
  • Keep endpoint responses small enough to understand from a terminal.
  • Add project notes that explain tradeoffs instead of only linking source code.

Lessons

  • Readable examples matter more than broad endpoint count.
  • A good project page should explain constraints before showing the stack.
  • Local setup instructions are part of the product experience.

Proof trail

Assumption to lesson, not just screenshot to stack.

Assumption

A local explorer is better for learning than a static list.

Experiment

Shape endpoints around searchable problem metadata and short response examples.

Result

The project becomes easier to explain as an API-design case study.

Lesson

Developer-facing projects need documentation surfaces, not only implementation.

Assumption

Small response payloads improve trust.

Experiment

Keep examples terminal-readable and move detail into linked notes.

Result

The public page can show constraints without overwhelming the visitor.

Lesson

Portfolio proof improves when data contracts are visible.