Case Study

Worker Connect

Government Workforce Platform (NYC OTI)

Zero downtime refactoring with improved workflow performance

Role

Full Stack Developer

Stack

React.js, REST APIs, Performance Optimization, Legacy Codebase

Timeline

Ongoing (2026)

Introduction

Worker Connect is a government workforce management platform used by NYC agencies. The project involved modernizing a legacy React frontend to improve stability, performance, and maintainability — all while keeping the live system operational.

Problem Statement

Performance bottlenecks, recurring bugs, and an unstructured legacy frontend slowed delivery and risked data inconsistencies across critical workflows.

Scope

Brownfield refactoring of the React frontend — module-by-module modernization covering API integration patterns, component modularization, code splitting, and bug elimination without disrupting production.

Target Audience

NYC government agencies and staff who rely on the platform for daily workforce management operations.

Functional Requirements

Module-by-module refactoring of legacy React components
Code splitting for improved page load performance
Standardized API integration patterns across the application
Component modularization for reusable, maintainable code
Critical bug fixes for data consistency improvements
Zero-downtime deployment strategy

Challenges

Refactoring live production code without downtime or data loss
Untangling tightly coupled legacy components safely
Improving performance within existing architecture constraints
Maintaining backward compatibility during modernization

Solution

Refactored module-by-module to standardize API integration, eliminate critical bugs, and modularize components while keeping production stable. Each module was isolated, modernized, and deployed incrementally.

Technical Overview

React frontend refactoring focused on restructuring API integration patterns, implementing code splitting, and modularizing tightly coupled components into reusable patterns for long-term maintainability.

Advantages

Zero downtime throughout the refactoring process

Eliminated recurring bugs improving data consistency

Improved performance via code splitting

Modular component patterns enabled faster feature delivery

Standardized API integration reduced maintenance overhead

Improved developer experience for future work

Limitations

Scope constrained by backend architecture
Full modernization requires ongoing incremental work
Some legacy patterns remain in less-critical modules

Outcome

The refactoring improved stability, eliminated recurring bugs, and boosted performance — all achieved with zero production downtime. The modular architecture now enables faster feature delivery.