COBOL & VB6 In the same semester?

Does taking those two in the same semester make me crazy? I've only had a couple classes of each, and the VB doesn't seem that hard yet but we've done minimal code in each class. This is actually my first time taking any programming but I have enough common sense & computer sense to figure the small program we've had to do so far.

So basically I would like to know if you guys would really recommend me taking both or would I be better off taking them separately? Thanks for any input https://www.sharkyforums.com/images/.../2005/06/5.gif

------------------
Wolfs Rig
7575 3DMark2K1

Before I start, just remember that COBOL IS THE DEVIL!. But seriously, COBOL is really messy and even to experienced C/C++/Java programmers it can be challenging. I read a little bit of it and I just didn't want to do it anymore, lol.

I never learned alot of Visual Basic, just the basics. Seems easy enough to consider it a passive class.

So, if I was you, I would do it. It might be a little work if you have never had any programming experience, but alot of people say VB is a good starting language.

So good luck with everything.

------------------
## root is the greed of all evil ##

Quote:

---

Originally posted by biosx:

So, if I was you, I would do it. It might be a little work if you have never had any programming experience, but alot of people say VB is a good starting language.

---

wasn't it Dijkstra who said that anyone who has written more then a few lines of Basic code is ruined for life and can't be taught how to program?


https://www.sharkyforums.com/images/.../2005/06/5.gif

------------------
I want an OS, not a hobby...

Take 'em both! COBOL is cake! I've been programming in COBOL for eight years, and I think it's a pretty simple language.

I have to agree with biosx, COBOL is sucky, though if you find the right job you will be making tons (mainly because no really uses/knows it these days). I took on COBOL class and it was easy, but that was because it was an intro programming course and it just so happened to be with COBOL. COBOL could be very hard I would assume in a more advanced class. If its an intro type course COBOL wont give you trouble if you already know programming concepts, the rest is just syntax. Right? lol https://www.sharkyforums.com/images/...2002/02/10.gif

------------------
-= SySTeM =-
Athlon 850 | | Asus A7V133A
Radeon 7500| | 256 PC 133 Micron
SoundBlaster XGamer 5.1 | | WD 20gig 7200
LiteOn 16x | |Enlight 7237 300 watt psu

Yeah, they are both intro courses and don't seem to be that bad so far. Hopefully they'll stay reasonably understandable though, don't need to be reworking my schedule 6 weeks into the semester https://www.sharkyforums.com/images/.../2005/08/2.gif.

I took VB w/ my friend just because he's graduating soon and we never took class together before, and he already had a little trouble on the first project and was looking for me to help him(I kinda breezed through it https://www.sharkyforums.com/images/.../2005/06/5.gif)...I can see where this is gonna go already https://www.sharkyforums.com/images/...2002/02/10.gif

edit-smiley

------------------
Wolfs Rig
7575 3DMark2K1

[This message has been edited by blackwolf (edited February 06, 2002).]

Take em both. I took COBOL in high school, and it's the easiest language to learn after BASIC. Visual Basic is more difficult *conceptually*, since it is *somewhat* object-oriented and event-driven. In contrast, COBOL porgramming is strictly top-down, procedural. The hardest thing in COBOL is printing. Use graph paper if you have to. I've programmed in both languages professionally.

Not many COBOL programmers are swimming in money, nowadays, unless you're privy to the Vantage system, which drives the insurance industry. I knew a few contractors that got $100 to $300 an hour b/c of y2k, and that was shortlived.

Best advice I can give is to study hard and remember that you don't get points deducted for asking your professors questions inside or out of the classroom. If you've declared your major, you really should be asking your C.S. advisor too, but ultimately understand that you know what is best for you!

------------------
Don't eat the yellow snow.

Intro courses? Hell take another couple of languages while you're at it :)

COBOL is not a messy language. In fact it's far from it. Out of the several procedural languages I know, it's still the only one I actually don't mind looking at when the code reaches the 5,000+ line stage; even if it is wordy.

It's not difficult either. However, many people make mistakes when it comes to using numeric, alphanumeric, and comp-3 fields. And that carries over into bad design of datasets.

The hardest part of learning COBOL is when your platform is a mainframe, because you have to learn Job Control Language -- and most people absolutely loathe it. On a PC it's pretty straightforward.

Anyway, I did COBOL for Y2K because that's where the money was at. Had one other COBOL contract after that, and they are still around. But if you're going to work in the language you really need JCL/DB2 (or more rarely IMS) skills. Probably not worth it unless you're interested in client-server apps where there is a mainframe backend (doubtful if you're under age 30).

Good luck.

First off, I've got to thank everyone for their advice & wishing me good luck :).

I'm definitely going to stick with both of these through the semester, as I definitely think I can handle them. The only problem I can see in the future is with the COBOL, as the professor is a moron :D. He has a huge emphasis on flowcharts *vomits*, and also likes to spend alot of time writing the code on the board when everyone HAS IT INFRONT OF THEM! So the class runs from 645-925p, and last class he lectured until about 845, and then when he attempts to walkthrough it w/ us on the screen, someone asks a moronic question(3/4 is only taking it because they HAVE to)and he'll spend 10-15 minutes trying to help them out, so by the time he gets back to his computer, the class is over and he leaves all the work on us without going through anything and we're all like :confused:. Ahh well, hopefully I'll be able to pick up most of it myself without having to rely on him. Again, thanks for the replies everyone :)