Every project has a point where the obvious route stops working. These ten stories follow what happened next: the constraint, the choice, and what the choice made possible. Employers remain unnamed.
Data performance
From about 2 seconds to 800 milliseconds
Two seconds is long enough for a service to interrupt the flow of a task. In this production system, the delay was already visible in important user journeys.
I traced the work into PostgreSQL and treated the data path as a whole: partitions, indexes, triggers, and persistence. After changing it, I measured against the original baseline rather than relying on a faster-feeling interface.
Average service response fell from about two seconds to about 800 milliseconds.
Business continuity
A working alternative in two weeks
A connectivity restriction cut off a communication tool the team depended on. Waiting for access to return would have left a real gap in daily work.
I built an alternative route: a cross-platform tunneling app and browser extension, researched, tested, and deployed with Rust, Go, Tauri, and Vue. The solution had to work across the devices people already used.
The workaround restored access and reduced related recurring infrastructure costs by about 98%.
Offline data
Product workflows without a connection
A lost connection should not mean lost work. The difficult part was preserving live changes while the network was unavailable, then making sense of them when it returned.
I used IndexedDB to hold real-time events locally and built a reconciliation layer for complex object state. The workflow could keep moving before synchronization was possible.
Core workflows could continue offline and synchronize when connectivity returned.
Frontend architecture
Clear boundaries for parallel delivery
As more developers joined, shared data flows became a point of friction. Features needed room to evolve without every change crossing the same boundaries.
I gave the Vue application explicit feature boundaries, centralized events, and predictable ownership of data. That made the architecture useful to the team doing parallel work, not just to its original author.
Developers could work in parallel, and the structure continued beyond the original team.
Developer experience
Environment handoff in one command
A development environment with too many manual steps turns a new teammate’s first day into a troubleshooting session. The setup itself had become work.
I moved the repeatable steps into Git hooks, Bash, and CI, then documented the remaining decisions. The handoff became a command someone could run instead of a list they had to memorize.
New hires could prepare the environment with a single command on day one.
CMS and SEO
An app-like site with editable content
The site needed the ease of a CMS, the discoverability of ordinary pages, and the fluidity of an app. Losing any one of those would have weakened the experience.
I joined Vue to PHP and WordPress through custom hydration, routing, and content handling. Editors kept their workflow while visitors could move through the site without a full reload.
The site kept CMS workflows and search-friendly URLs while gaining app-like behavior.
Campaign delivery
Mobile campaign delivered in three weeks
A mobile campaign needed venue information, participation tracking, analytics, and messaging on a short delivery schedule. The required Angular stack was new to me.
I spent three days getting productive in the framework, then built the application and its service integrations. The schedule demanded a working whole, not isolated screens.
The application was delivered in three weeks after a three-day ramp-up on the framework.
Water awareness
3D storytelling across browser limits
The creative direction called for animated 3D water storytelling. At the time, WebGL support was uneven, so a scene that worked in one browser could fail to tell the story in another.
I took on modeling and rendering work in Blender to create narrative sprites, then paired those with WebGL where live 3D was dependable. The technique followed the story through the browser limits.
The visual story could run across browsers without relying on live 3D for every scene.
Women's safety
A discreet exit in a moment of risk
For someone reading a women’s safety campaign in a risky setting, leaving the page could be as important as finding it. A conventional exit could leave an obvious trace in the current browsing flow.
I used the History API and popstate to manage the campaign page’s own history entry during a quick exit. The design focused on a discreet path away from the page; it did not claim to clear the browser’s entire history.
The exit flow reduced the chance of the campaign page remaining as an obvious entry in the current browser history.
Mobile AR
Preview products in their surroundings
A product image can show shape, but it cannot show how that shape sits in a customer’s space. The missing context was the room around the product.
I translated 3D design assets into mobile WebXR and AR previews with Vectary. The phone camera became the way to inspect scale and placement in context.
Customers could place and inspect product models through a smartphone camera.
