// case file 10 · Software

AceBuddy

Study tools students open every day: marketplace, onboarding, notes editor, contributor and admin surfaces.

RoleFrontend-primary contractTimelineOct 2025 – Jun 2026StackNext.js + ReactNDAsafe summary only
Visit AceBuddy ↗
// 01 the problem

A fast-moving edtech product needed features landing continuously without breaking what students already used.

// 02 how it works
  1. Step 01

    Marketplace, shipped behind feature flags.

  2. Step 02

    Onboarding: invite codes, OAuth, email + verification.

  3. Step 03

    Notes editor with Markdown, images and math.

  4. Step 04

    Collections, contributor and admin surfaces.

// 03 decisions that mattered
01

Flags over commented-out code

Incomplete features shipped dark kept main deployable while work landed piecemeal.

02

Tokens moved to memory

Adapted frontend auth when access tokens left persistent storage.

// 04 results
NDAsafe summary only
Dailystudent usage
Mainalways deployable
// 05 takeaway

Feature flags did more work than any single line of code.

Next.jsReactTypeScriptTanStack QueryFeature flags
// artefacts
Visit AceBuddy
// contact

Let’s talk

Open to software engineering and AI automation roles, plus selective contract work. I read every message.

psst, click it
● DRAFT

Show me the copy-paste.
I’ll tell you if it should be a system.

01
02
How often?
03
Which tools?

Hiring? Tell me about the team.
I’ll tell you where I’d help first.

01
02
03
Timeline
04

You get a reply within 24 hours: whether it should be automated, what I’d use, and a rough timeline.

You get a reply within 24 hours.

Email Henry
LinkedIn ↗GitHub ↗X ↗Résumé ↗