Legacy Application Maintenance

Work this role can support

• Capture current behavior in characterization tests before changing a named module
• Repair reproducible defects while preserving documented interfaces and file formats
• Replace one deprecated dependency at a time with compatibility and rollback notes
• Document build steps, runtime assumptions, scheduled jobs, and external integration points

Controls to set first

• The owner approves scope, dependency upgrades, data conversions, and release timing
• Each patch starts from a tagged baseline and excludes unrelated modernization work
• Representative fixtures replace live records in development and regression tests
• Release review includes a rollback package and smoke checks for named legacy workflows

Practical launch plan

1. Record supported runtimes, build commands, deployment topology, and known constraints
2. Create a reproducible environment with pinned dependencies and representative fixtures
3. Select one low-blast-radius defect with baseline behavior and acceptance checks
4. Compare baseline and patched behavior before the owner approves a release and rollback window