← Back to work

Case study · Formative work

The consultancy that became a school.

Hemaka was where web work stopped being one clean job title. It was animation, JavaScript frameworks, production constraints, client context, QA, support, and judgment — often in the same day. It taught me how to keep moving when the work asked me to wear a different hat.

Role
Frontend engineering, animation, QA, product support
Materials
SVG motion, JavaScript frameworks, responsive UI, production fixes
Lesson
Learn the next tool, then use it responsibly.
Talk through a technical build Visit hemaka.com
Hemaka pyramid logo animation with black and gray slices loading into place
One-time logo motion captured from the Hemaka homepage loading sequence.
Challenge

Learn inside real production pressure.

The education was not abstract. Every new framework, animation detail, layout problem, and browser issue had to resolve into something a real person could use. That made the learning stick: concepts mattered only when they improved the shipped experience.

Approach

Prototype, inspect, ship, repeat.

I learned to move between rough prototypes and careful implementation: testing motion timing, reading unfamiliar code, tracing bugs through the stack, and translating design ambition into maintainable frontend work instead of decorative effects.

Endpain case-study vines growing around the logo and content card on the Hemaka website
Endpain interaction capture from hemaka.com: taps generate new SVG vine growth around the case-study content.

What it taught me

Technical range is a design skill.

Hemaka made me faster because it made me broader. The work trained me to see a site as a system: motion, copy, state, layout, deployment, and support all influencing each other. That is still how I diagnose and build websites now.

Animation

SVG, staggered motion, timing curves, and interaction that makes an interface feel intentional.

Frameworks

Component thinking, JavaScript architecture, state, routing, and the tradeoffs behind library choices.

Production Judgment

Debugging what actually broke, reducing fragile code, and making decisions that survived launch.

Wearing Hats

Switching between engineer, designer, QA, client translator, and problem owner without losing the thread.

Hemaka was a school in itself: the place where I learned that the best web builders are part craftsperson, part systems thinker, and part calm problem solver.

Outcome

A foundation I still build from.

The lasting result was not one screen or one technology. It was a way of working: stay curious, understand the moving parts, make the browser do something precise, and keep the user experience intact when the work gets complicated.

  • Built comfort with animation-heavy, JavaScript-driven interfaces.
  • Learned to evaluate frameworks through production constraints, not hype.
  • Practiced owning ambiguous work across design, code, QA, and support.
Build with that level of care
Hat stack
  • Animation
  • Frontend architecture
  • Responsive detail
  • Debugging
  • Client context
  • Launch support

Have a build like this?

Bring the moving parts: animation, frontend, weird browser behavior, half-built flows, or a site that needs better judgment before launch. I will turn it into a practical plan and reply within a day.