cobol traumatized me

แชร์
ฝัง
  • เผยแพร่เมื่อ 23 พ.ย. 2024

ความคิดเห็น • 4

  • @NotMarkKnopfler
    @NotMarkKnopfler วันที่ผ่านมา +1

    Hello! Just stumbled on your video somehow - this is interesting to me personally as I've considered learning COBOL for professional reasons as COBOL positions can be lucrative. So I'll be watching this video in its entirety over the course of the weekend. Have a great weekend - maybe stay away from the computer for a couple of days to detox from your experience 🤣

    • @ellyse7777
      @ellyse7777  วันที่ผ่านมา +1

      I'm just staying away from COBOL for a few days! But you know, I think once we get going, this can be fun. What's closer to weilding magic than using mainframe commands?

    • @NotMarkKnopfler
      @NotMarkKnopfler วันที่ผ่านมา

      @@ellyse7777 Yes - agree - it should be fun. Just remember, all the shite that you will have to go through to run COBOL is not an artefact of the language. It's the fact that you're coding on a mainframe (or a virtualised mainframe) and the mainframe is very very strict about how things are done. You'll submit your code for compilation and execution using JCL (job control language) (everything on these mainframes is a job, which is executed and logged, so you can go back in time and see who executed what, when, what happened, how long did it take, how much CPU did it use etc). So, you'll be thinking "Why the heck do I have to do this/that" etc... But that's not COBOL - it's the platform your coding on. If you installed a COBOL compiler locally the workflow would be similar to any other compiled language. It's just the fact that you'll be running on a mainframe that will make it painful!
      Personally I love the thought of running all this mainframe stuff - but I'm ancient - 54 years old, and have done years of assembly language programming with arcane, self-built tools, so it's no biggie for me.
      Looking forward to following your series. Subbed 🙂