KahWee Teng

KahWee Teng · Staff software engineer

Complex systems deserve clear thinking.

I work on frontend systems and developer experience, then write about what the diagrams leave out: migrations, performance, AI-assisted engineering, and the tradeoffs that make software last.

Start with selected work Read the case study
A field-guide drawing of a pine-lined mountain trail and signpost

Bearings

KahWee in 30 seconds

Role
Staff software engineer
Focus
Frontend systems + developer experience
Journal
88 field notes since 2016
Perspective
Singapore → San Francisco

Working terrain

Experience, shown through the work.

Three recurring questions guide this journal: how systems change, how tools change the work, and what survives outside a demo.

01 · Systems

Make migrations legible

React, TypeScript, performance, and framework changes measured in real implementation work.

Follow the frontend route 02 · Practice

Test the work around AI

Agents matter, but so do review habits, cost controls, context, and the harness around the model.

Follow the AI practice route 03 · Fieldwork

Prefer evidence to demos

Cloudflare, self-hosting, and home infrastructure observed where constraints are harder to hide.

Follow the infrastructure route

Trailhead

Selected work and thinking

A short route through the archive: measured comparisons, difficult migrations, and lessons that still hold.

Explore the full journal Read the professional case study

From the trail

Latest field notes

Browse all 88 posts
Essay

AI Pricing Is Becoming UX

GPT-5.6 turns capability into a price ladder, while Codex Spark turns speed into a separate button. AI pricing is becoming part of the interface.

Field note

Claude’s Guardrails End at Claude

Closed-model guardrails remain tied to the provider, even as comparable open weights spread. Public safety needs controls that survive that reality.