Thank you for getting involved in this great advice. I knew I wasn’t actually going to pursue a professional career in COBOL; in fact, it was just a way to just

Thank you for getting involved in this great advice. I knew I wasn’t actually going to pursue a professional career in COBOL; in fact, it was just a way to justify my learning of this language and even other languages from the same era. I'm trying to immerse myself in the mindset of programmers from that time, in addition to everything modern today. I have a certain fascination for old things that have been abandoned—it’s often a legacy that shouldn’t be ignored, especially if it took a long time to develop or if it has matured significantly. It would be quite narrow-minded not to take an interest in what was done in the past to satisfy one's thirst for learning. But COBOL itself would really be my last option if I had to look for a job, though it’s still worth paying attention to its market demand. Fortunately, there are many other jobs in programming. Thank you again for contributing to my growth in both computing and professionalism—I’m still far from reaching the end of my learning journey. In the end, I was right to make this post.