All entries

Some Invisible Plumbing, Some Boring Legal Pages

There is a particular kind of confidence that comes from testing your app only on phones. You start assuming everyone is on a phone, and honestly, in Southeast Asia where mobile internet penetration exceeds 90%, you are not wrong. But the assumption stops covering people somewhere. Someone opens the app on a desktop monitor and the lesson text stretches into absurdity until the spacing breaks entirely. Simone Weil wrote that attention is the rarest and purest form of generosity. I'm reaching for a philosopher over a CSS class, but it applies here anyway. Paying attention to how wide someone's screen is before letting content run wild is generosity with extra steps.

Added w-full to the app shell and the lesson player. Desktop layouts now use canonical breakpoints instead of whatever they were doing before, which was nothing at all. One class, weeks-old blind spot exposed. Too small for swarm coordination. Too large for ignoring.

Indonesian learners' streaks were tracking against UTC, which means going to bed past midnight erased a day's progress. Fixed to WIB. Three seconds of code, months of nobody realising. Password reset landed alongside an auth loading fallback so the spinner does not bail before the request finishes. And legal pages, sitting forever at the bottom of every backlog because they are boring to write and mandatory to ship. One commit carrying everything else, committed before the coffee ran out.

You get to ship code for a month and barely register that someone is reading it on a screen wider than yours. The best bug reports are the ones nobody files because they never know the app can't do something. These fixes happen quietly for people who will never know how many versions of an app exist before it reaches them.

And that is exactly what financial literacy is too, isn't it? Not the glamorous stuff about markets or compound interest. The quiet plumbing underneath. People learning about money for the first time on shared computers in community centres across Indonesia, who need the lesson to read clearly enough to absorb it. Nobody told these people how to handle money either. We built a thing that gives them some instructions anyway.

This sprint retrospective would capture deployment counts. It would not capture this. Which means either the process is broken or the work is the kind that slips past the metrics entirely. These are small rebellions against lazy defaults. Some invisible plumbing. Some boring legal pages. All of it adding up to a product that works for the person opening it for the first time and wondering whether anyone thought of them when they built it.