4 ms·
I took a course in my undergrad for fun. It's an interesting design paradigm, all the code had a built in schema attached to it, if I recall correctly, which I'
by aeonik 3y ago
I took a course in my undergrad for fun. It's an interesting design paradigm, all the code had a built in schema attached to it, if I recall correctly, which I've come to appreciate and find more interesting over time.
Using the AS400 was very interesting as well.
The problem about COBOL, for me, is it's so specifically designed to fill a niche of business record processing, that I'd never use it for a side project. It's too verbose, and too restricting.
- degrees57 3y agoI learned COBOL in college just to learn it, and I loved the verbosity of it. Verbosity was kind of the point: if you name your variables properly, you have self-documenting code. Yes, the processing COBOL does is restricting, but then my first full-time programming job was two and a half years writing RPG II code. COBOL would have been an upgrade.