41–50 of 232 posts
Earlier quoted context omitted.
What's wrong with that? I have seen it often in books and other places.
I suspect they are more suspicious of `pandas` than the syntax of the import. But, I'm also curious as to why.
Earlier quoted context omitted.
At least they will pay you well.
And you will not have to deal with the ego of the current programmers that pretend they now everything about any existing programming language, paradigm and technical stack (where I include myself and because that is what is demanded)
I do not get all the hatred. The idea behind COBOL’s syntax is the same as SQL’s: it is merely yet another “Structured English Query/Programming Language” designed, initially, for non-programmers to be able to describe in words what it is they would like to accomplish in a way they could be understood by the computer.
COBOL is not an interesting programming language these days, and you should not learn it unless you need it for your current job.
> [COBOL was] designed, initially, for non-programmers to be able to describe in words what it is they would like to accomplish in a way they could be understood by the computer.
Let me tell you a secret. It doesn't work for non-programmers. The complexity of "Z = X + Y" is no more or less than "ADD X TO Y GIVING Z", and bugs will happen at the same rate with either syntax. The added verbosity will only annoy you.
Another myth surrounding COBOL is that as its programmers age, there is a lack of them and therefore COBOL jobs are high-paying and you should learn it to make good money. The reality: I've never met a really wealthy COBOL programmer -- or rather, one who was wealthy because he/she knew COBOL. That's not where the money is. COBOL jobs are not particularly well-paying, and there are young people learning it, and no, they don't get awesome paychecks.
Earlier quoted context omitted.
At least they will pay you well.
And you will not have to deal with the ego of the current programmers that pretend they now everything about any existing programming language, paradigm and technical stack (where I include myself and because that is what is demanded)
Earlier quoted context omitted.
What's wrong with that? I have seen it often in books and other places.
I suspect they are more suspicious of `pandas` than the syntax of the import. But, I'm also curious as to why.
Earlier quoted context omitted.
I say YES do it, learn COBOL and Mainframes, don't listen to others who say Mainframe is a thing of the past, it's here to stay. Just talk with leading positions in Insurance/Finance government maybe?, they are more then happy to find someone who is motivated and eager to learn, AND they have the money and time to support and build-you-up (Training mentors certs licenses etc.).
Mainframes are alive and well, they just have new names like AWS, GCP, Azure...
Earlier quoted context omitted.
Just curious, but why is COBOL the first language that you think about for this?
Because I already know: C, C++, Obj-C, C#, Php, Lua, x86 ASM, ARM ASM, Linoleum (some ASM-like esoteric languagE), BASIC (not VB), Java, Python, JS, MushCODE (it is derived from LISP), SQL and some application specific scripting languages. I started coding when I was 8, I am 32 now, and in my government-issued employer list, I had zero employers. My dad knows COBOL and MUMPS, and kept talking about how horrible they…
With a portfolio like that, you might want to look at why you can't get a job. You sound capable enough on the technical front, so there must be something else that's preventing you from advancing your career.
Sometimes I wonder if I should learn COBOL just so maybe I can get my first real programming job. (and no, I am not joking...)
You absolutely shouldn't learn COBOL before knowing which job you're aiming for. COBOL isn't an interesting or particularly useful language to learn.
Earlier quoted context omitted.
Just curious, but why is COBOL the first language that you think about for this?
Because I already know: C, C++, Obj-C, C#, Php, Lua, x86 ASM, ARM ASM, Linoleum (some ASM-like esoteric languagE), BASIC (not VB), Java, Python, JS, MushCODE (it is derived from LISP), SQL and some application specific scripting languages. I started coding when I was 8, I am 32 now, and in my government-issued employer list, I had zero employers. My dad knows COBOL and MUMPS, and kept talking about how horrible they…