Heh, you are correct, it’s always the why, even in a language you work with every day. It’s hard even if it is you who wrote it if you don’t remember the why, and then add an unknown code style and an unfamiliar domain. And on top of that maybe multiple projects interacting and I feel the burnout threaten I have to think of something else for a while 🫨
Learning to COBOL is not itself that hard.
Understanding decades of “business” logic is.
It isn’t WHAT it is doing, it’s WHY it is doing it that makes these systems labyrinthian.
Also afaik they don’t get paid that well which is part of the problem.
Heh, you are correct, it’s always the why, even in a language you work with every day. It’s hard even if it is you who wrote it if you don’t remember the why, and then add an unknown code style and an unfamiliar domain. And on top of that maybe multiple projects interacting and I feel the burnout threaten I have to think of something else for a while 🫨