Gemastik → Enterprise
The moment the pivot happened wasn't a decision. It was a Tuesday in late 2024, sitting in a coffee shop near campus, looking at the Gemastik 4th-place certificate on my phone, and noticing I felt — not deflated exactly — finished. Two years of pushing toward national animation work and the door had opened just wide enough for me to see what was on the other side. The view didn't pull me through.
A month later I'd taken the Hino Motors offer. Three months after that I was building enterprise C# / ASP.NET MVC systems for 1,500 plant employees. The pivot looked sudden from outside. From inside it had been telegraphed for a year and I just hadn't said it out loud.
This post is what that transition cost, what it kept, and the parts of an animation background that turned out to matter for engineering work in ways nobody in engineering school had warned me about.
what gemastik was
For non-Indonesian readers: Gemastik is Indonesia's national-level student computing competition, run by the Pusat Prestasi Nasional under Kemdikbud. The animation track is small, brutal, and intensely competitive — finalist in 2023, 4th in 2024 puts you adjacent to but not inside the very top tier of student animators in the country.
The skills the track demanded weren't really about software. Blender mattered, After Effects mattered, but the expensive part was always the timing — frame-level decisions about when to cut, when to hold, when to break expectation. Animation has a specific cognitive demand around compressed time that I didn't know I'd internalized until I left the discipline and noticed I missed it.
the pivot — what actually changed
The cliché answer is I fell out of love with animation. That's wrong. The accurate version is closer to I admitted the long-term math wasn't going to work for me.
The math was: animation as a profession in Indonesia, for someone who isn't independently funded, looked like 5-10 years of grinding through studio work at rates that would not cover Jakarta rent. The work I'd want to do — the experimental, craft-forward bits — were 90% unpaid passion projects. The work that paid was advertising and TV-level animation that didn't excite me.
Engineering, specifically, paid 3-5x what equivalent-experience animation paid in Indonesia. It also let me work remotely with overseas teams. The combination — better compensation, geographic flexibility, work I could plausibly enjoy — was the thing that made the pivot make sense, not a single moment of disillusionment.
The honest version: I'd been hedging the whole time. The CS undergrad I was finishing at UGM was the hedge. When the hedge started looking better than the original bet, I quietly switched. Two years of animation work didn't become a waste — it became the angle I now bring to engineering — but the primary career path changed.
what survived the pivot — animation skills that became engineering skills
Three muscles from animation that turned out to matter more in engineering than I'd expected.
Timing. Animation is fundamentally about controlling perceived time. Hold for two frames. Cut on the action. Anticipate, then release. In engineering, the same instinct shows up in scroll choreography, loading states, micro-interactions, the 200ms gap between user input and visible response. A loading spinner is a frame of animation. The decisions about when to show it, when to hide it, what to ease toward — they're animation decisions, not engineering ones.
Composition. A frame has visual weight, focal points, hierarchy. So does a UI. The same instinct that tells an animator the eye is going to the wrong place tells a frontend engineer this CTA is being undercut by the heading next to it. Composition was the skill I'd assumed wouldn't transfer. It transferred completely.
The discipline of doing the same shot fifty times. Animation is iterative in a way most engineering isn't. You produce a shot, watch it, find the timing wrong, redo it. You don't ship a shot at v1. The discipline of I will keep working on this until it's right — not "until the deadline" but "until it's right" — is the muscle that makes craft frontend work different from competent frontend work.
what i lost
The instinct I'd been training for two years that I haven't had to use in 18 months is the frame-by-frame patience — the willingness to spend an hour on a quarter-second of timing. Engineering work, even craft frontend work, doesn't quite demand that. The closest analogue is debugging a subtle race condition, but the texture is different. You're hunting a bug, not iterating toward a feel.
I miss it. The atrophy is real. I notice it in the way I now reach for "good enough" decisions on motion-design work where, two years ago, I would have spent another evening getting it right.
The thing animation taught me that engineering school didn't: ten "good enough" decisions in a row don't add up to one great one. You have to be willing to spend extra time on the one that matters most.
for the student reading this
If you're in the place I was in late 2024 — looking at a small win in a craft you love and starting to feel the long-term math get awkward — three things I wish I'd known.
The pivot doesn't have to be a betrayal. I felt for months like leaving animation was some kind of moral failure, like I was abandoning a calling. It wasn't. Skills compound across disciplines. Two years of animation work made me a better frontend engineer. Two years of frontend work will probably make me a better animator if I ever come back.
The hedge isn't shameful. I'd been finishing an engineering degree the whole time. The shame I felt about being "not fully committed" to animation was misplaced. The hedge was the thing that gave me options.
Don't make the pivot until the door on the other side actually opens. I didn't quit animation. I accepted an engineering role and the animation work decayed naturally as my time filled. Quitting the thing you love before you have a concrete next thing — even when the long-term math is clear — creates regret that the pivot itself doesn't.
The 18 months since have been the most professionally productive of my life. The instinct I bring to engineering work — the timing, the composition, the iteration discipline — wouldn't exist without the two years of animation. The pivot didn't subtract anything. It just changed which muscle was loading.