My first shipped product came while I was still in vocational high school. At PT. Autochem Industry, I was not doing toy assignments or sandbox exercises. I was asked to build a real e-commerce application inside an actual company environment, and that forced me to learn fast.

CodeIgniter became the framework that taught me how a business system is stitched together: routing, controllers, forms, data persistence, and the quiet discipline of keeping flows predictable. I was still early enough in my journey that almost everything felt new, which meant every bug was also a lesson in how software breaks in the wild.

The biggest shift was mental. I stopped thinking of programming as a set of disconnected coding exercises and started seeing it as operational work. The app had to support a workflow, not just render a page. That small change in perspective stayed with me long after the internship ended.

Looking back, the product itself was less important than what it unlocked. Shipping something during high school made the career feel real. It gave me proof that I could work through uncertainty, contribute in a business setting, and keep going even when the implementation details were still above my level on day one.

That internship set the tone for the rest of my career: get close to the business problem, accept that the codebase will never start clean, and ship anyway. Everything that came after was a more complicated version of that same pattern.