I didn't grow up wanting to be a developer. I grew up wanting to take things apart and find out why they worked — clocks, radios, arguments, it never much mattered which.

Informatics Engineering gave that instinct a name and a degree to go with it. Sarjana Komputer: four years of being told that every clever thing you build will one day be maintained by someone tired, and that you should write it for them.

I went where the work was felt. The frontend is the only part of a system a person ever touches, and for five years I have spent my days on the side of the screen where a wrong decision is not a stack trace but a small, unexplainable friction.

Motion, state, the half-second before something responds. I learned to treat those as engineering rather than decoration, because to the person holding the phone there is no difference between slow and broken.

What kept pulling me down was the part I enjoyed most: analysis, and the shape of a system before any of it exists. Schemas that hold under load. Transaction boundaries that are exactly right. Logs that make sense at three in the morning.

So for the last three years I went and learned it properly. Not to leave the surface behind, but because you cannot design a good one without knowing what it is standing on.

Five years in the trade, five of them frontend, three of them backend — the arithmetic overlaps because the learning did. I have stopped believing that better products come from better frameworks; the tools change every eighteen months and the hard parts stay exactly where they were.

What moves the work forward is better questions, asked earlier, by someone willing to hear an inconvenient answer. That is the part I am still practising.