Yeah nah maybe fix the bugs before swapping the average COBOL dev for the average Java dev.

sometimes if the bug exists for enough time it is intended behavior

Absolutely, and you'll have all kinds of fixes for the symptoms throughout the project.

COBOL isn't hard, the tooling around it on old systems are a pain though.

	▲	Maxion 16 minutes ago \| parent [-]
		Anything running on COBOL to day is a large enterprise system. You'll have reports running in other systems in subsidiary companies that rely on bugs in the upstream cobol code.

Indeed, there may even be a whole lot of code that depends on it.

	▲	wwind123 37 minutes ago \| parent \| next [-]
		Yeah. Bug-for-bug migration is a real thing in large code-bases in the industry. You want to replicate all behavior of the code regardless whether the behavior is a feature or a bug. See Hyrum's Law: https://www.hyrumslaw.com/
	▲	nkjoep 27 minutes ago \| parent \| prev [-]
		Yep, and when it’s about money you don’t want any unexpected.