$ cat projects/vimo.mdx
Vimo - Government SaaS Modernization
Technical ownership across childcare and insurance platforms: AI-assisted legacy migration, shared React libraries, accessible form systems, role-aware workflows, testing, and performance work.
React 19 · TypeScript · Nx · RTK Query · React Hook Form · Zod · Vitest · MSW · 2024 · live
Daffodil Software · Feb 2024 - Present
At Vimo, I work across government technology platforms for childcare and health-insurance administration. The frontend spans an Nx monorepo with reusable libraries and newer React applications, alongside legacy JSP, Angular, and React code that is being modernized incrementally.
what I own and contribute
- AI-assisted legacy migration framework - designed and own a developer-controlled workflow that traces legacy dependencies, documents business rules, creates a reviewable migration plan, generates React-aligned code, and validates it with tests, builds, and manual/QA review. It has reduced comparable migration effort by approximately 50%.
- Shared React libraries - expanded React 19 and TypeScript libraries used by a 30-40 person frontend organization, including reusable form controls, layout primitives, hooks, responsive utilities, accessibility behavior, and Storybook examples.
- Accessible product workflows - built a resumable seven-step registration flow with React Hook Form, Zod, RTK Query, conditional validation, dynamic assisters, persisted progress, and role- and application-status-based access.
- Performance and reliability - migrated a condition-heavy Ticketing workflow from a mixed legacy codebase and helped improve its administrative load time by approximately 30-40%. Also diagnosed a React 19 incompatibility in a minified third-party integration and restored the affected production workflow through a targeted configuration fix.
- Technical ownership - guide two to three engineers on migrations, review approximately five to six pull requests weekly, and contribute to accessibility, testing, security, reuse, and business-logic standards.
how I work here
Architecture decisions are made with leads and teammates; I influence options, document choices, and turn them into maintainable feature structures. I expanded an existing shared library rather than creating its original architecture, and I implemented a lead-designed RTK Query authentication foundation while owning substantial session and inactivity behavior.
what stuck with me
- Legacy migrations succeed when the team can understand and verify behavior before any code is generated.
- Accessibility has to hold at both levels: individual components and the way those components are composed in a feature.
- A production incident is often an integration problem hidden behind an application symptom. Good debugging means following evidence across those boundaries.