
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.
Read the pieceKahWee Teng · Staff software engineer
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.

Bearings
Working terrain
Four recurring questions, each grounded in a piece that shows the decisions, evidence, and tradeoffs behind it.

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.
Read the piece
I wanted to keep a shared table component current without accepting migration work on faith. A side-by-side benchmark made the trade-off much easier to judge.
Read the piece
My Remix-to-React Router v7 migration touched 40 files and removed 591 net lines. Imports were easy; TypeScript took the time.
Read the piece
Adobe Animate kept the Flash timeline alive for HTML5, but the web moved on. Maintenance mode confirms the bridge could not hold.
Read the pieceFrom the trail
Removing SSR simplified Cubbly but delayed useful inventory. I compared four client-loading compositions and kept the one that made real route content 31–42% faster.

I removed React SSR from Cubbly because maintaining Lingui across the Worker and browser was not worth the speed it bought on a private application.

I use Hermes Agent to interpret and configure automations, then let Home Assistant or a script execute repeatable actions with visible failure states.

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.
