Isn't it a good case for visual programming? If you can't afford programmers, then you go for something less demanding and throw more cheap bodies at the problem.
My take on visual programming is it's easier to start out with, but you're quickly better off using a conventional language once you reach a certain scale or you need to manipulate your program in certain ways. Almost every time I see an expression builder in a UI, I think it would be better off with SQL syntax and autocomplete because the dropdowns get old fast, and SQL expressions aren't that hard.
Learning COBOL: A Journey for the Modern Programmer
61–63 of 63 posts
Re: Learning COBOL: A Journey for the Modern Programmer
#62Earlier quoted context omitted.
> The JCL is the harder part. Even its creators say JCL is the worst language ever invented.
And gave the main reason as "because we tried to not make a language so hard, the requirements evolved it into one in form of exceptions rather than design"
Re: Learning COBOL: A Journey for the Modern Programmer
#63I took a survey of historical programming languages course in college that covered FORTRAN, COBOL, SNOBOL, Prolog, SmallTalk, and several others of importance or uniqueness. Each section required a small practical program be written in that language, and we discussed each in its context of usage, 'family tree', syntax etc I guess I am saying programming history classes is where COBOL belongs.
This course sounds really interesting. Do you remember if there was a text book or if there is any online syllabus for it?