IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Sure, they *can* do real time
But most of what I've dealt with, they don't.

They guys who have been writing COBOL for 40 years are good at it. They would be good in any language. I'm talking about the average guys, working on the average apps. I don't know how COBOL is taught is schools today, except that I think it's only taught in India. (I've never talked to am American COBOL jockey under 40.) And those guys are completely wedded to nightly batch and quarterly release cycles.

But it's the business users who drive me insane. They just assume that's how it has to be, because all the computer guys they deal with have trained them and taught them the language. "Send me a sample file ... run the cycle ... how many records will you be sending ..."

You know, I don't think it's really a COBOL vs. $other issue. It's about people who don't get what databases are for and what they can do. And this goes for programmers as much as it does for business folks. I've seen guys re-invent sorting in Java, cursors in VB, foreign keys in C++, filter criteria in PHP.

I came up using SQL databases. When you have data, you keep it in a database, not a file. When you want data, you query a database, not a file. I deal every day with people who just don't think that way. And a lot of them think in COBOL.
--

Drew
New There's an incorrect meme there.
They guys who have been writing COBOL for 40 years are good at it. They would be good in any language.


Uh, no. If all you know is COBOL, any estimates of your ability in another language are a shot in the dark. In fact, you'd probably be rubbish. This, of course, applies to any language. Most recently, I've seen it with Java. Years ago I took over a small program in QuickBASIC written by my manager. He had a very COBOL-oriented programming mindset which was extremely evident in the code I threw away.

Like all languages, they teach a way of thinking. It's like learning a tool. Many programmers do not learn more than a small number of tools and often find themselves using the wrong tool to solve a problem. I saw it with programmers who got unnecessarily excited about sub-Selects in MySQL (when they were, in fact, a performance killer). I see it with programmers who think they understand the concepts of MVC or data-abstraction when actually they don't. I see it in programmers who believe Structs and Hibernate is The Way To Do Things and want to therefore radically alter a database's schema for no other reason than "it's wrong"... :-/

Wade.

"Ah -- I take it the doorbell doesn't work?"
New you must know my crew
New Fairy nuff
Great programmers, the ones who write trading systems that process hundreds of transactions per second, probably study multiple languages and styles. That they happen to be writing in COBOL is probably as much due to when they started programming as it does to the preexisting codebase.

But there is a COBOL way of thinking that can be incredibly limiting if that's all you know. And yes, that's true of any language.
--

Drew
     Happy Birthday COBOL - (lincoln) - (9)
         Re: COBOL and banks - (drook) - (8)
             Re: COBOL and banks - (lincoln) - (7)
                 excel ? -NT - (boxley) - (2)
                     Re: excel ? - (lincoln)
                     DEC PASCAL? -NT - (pwhysall)
                 Sure, they *can* do real time - (drook) - (3)
                     There's an incorrect meme there. - (static) - (2)
                         you must know my crew -NT - (boxley)
                         Fairy nuff - (drook)

Too hard to follow.
47 ms