GRADUATION
DIDN'T END
LEARNING.

Advanced patterns — performance, testing at scale.

It's the tool David reaches for first when turning an idea into an interface.

Ship a project using React Server Components.

Generics, stricter typing across larger codebases.

Fewer runtime surprises, clearer contracts between parts of a system.

Migrate StudyFlow fully to TypeScript.

Research methods for low-resource contexts.

The best interface is worthless if it solves the wrong problem.

Run a proper usability study for AgriLink.

Prioritization frameworks and roadmap thinking.

Wants to help decide what to build, not just how.

Own a feature roadmap end-to-end at work.

Query optimisation for larger datasets.

Most interesting product questions eventually become data questions.

Build a small internal analytics dashboard.

The basics, mostly for data analysis scripts.

Useful for the data side of product thinking.

Finish a short applied data-analysis course.

Design systems and component libraries.

Bridges the gap between design intent and frontend implementation.

Build a shared design system with a designer colleague.

Screen-reader testing and ARIA patterns.

An interface that excludes people isn't actually finished.

Audit CampusConnect against WCAG 2.2 AA.

Event tracking and interpreting product metrics.

Wants decisions grounded in what people actually do, not assumptions.

Instrument one personal project properly.