Florian Rand

Modernized a tightly coupled legacy Java application through an incremental migration that separated its UI, data processing, and automation integration.

• The Problem: A four-class Java application had accumulated more than 10,000 lines in a single class, combined unrelated responsibilities, had no automated tests, and depended on manual data ingestion and FTP-based deployment.
• The Intervention: Designed and implemented a phased migration using a translation layer, replacing the Swing interface with React, extracting Java services, automating CSV ingestion, introducing automated tests, and implementing CI/CD.
• The Outcome: Migrated the application progressively from the legacy implementation to independently maintainable services without planned interruption, replacing the original monolithic deployment and manual operational workflow.

Reworked a slow and expensive CI workflow by separating jobs, removing duplicated configuration, and parallelising Cypress tests.

• The Problem: A monolithic CI workflow provided slow feedback, with Cypress representing the main execution bottleneck and failures requiring the entire workflow to be retried.
• The Intervention: Separated the CI workflow into independent jobs, extracted reusable build scripts and modules, parallelised Cypress execution, and optimised slow end-to-end tests.
• The Outcome: Reduced E2E execution time by approximately 85% and cut CI expenditure by more than one-third.

Helped turn an unstable visual-template prototype into a working product capable of live editing and multi-format previews.

• The Problem: Rapid development had created significant technical debt, with fragile UI behaviour, limited coordination, and core features repeatedly breaking existing functionality.
• The Intervention: Introduced a more structured development workflow, refactored core platform components, adopted TanStack Query for server state and caching, and built the multi-format rendering engine.
• The Outcome: Reworked the platform and delivered a functional prototype in three months, including the core multi-format rendering experience.

Turned a large unstructured collection of speech therapy exercises into a structured catalogue integrated with the clinic's existing patient-management workflow.

• The Problem: Thousands of exercises existed as inconsistently named Office files, making them difficult to find, classify, and assign to patients through the existing manual workflow.
• The Intervention: Built Java tooling to extract and classify exercise content, extended the existing Access database and workflow, and migrated the file collection into a structured catalogue with direct patient-to-exercise links.
• The Outcome: Reduced exercise assignment from an hours-long manual process to minutes for straightforward cases while preserving the therapists' existing authoring workflow.

Turned a machine-dependent WordPress development process into a reproducible workflow that could be shared across developers.

• The Problem: Website development depended on one specialist's locally configured machines, with manual project setup, no source control, and manual deployments.
• The Intervention: Established a shared GitLab workflow, built reproducible development environments, introduced WordPress-specific tooling, and migrated existing projects into individual Git repositories.
• The Outcome: Reduced development environment setup from hours of manual configuration to a small number of commands and created a workflow that could be shared with additional developers.