"Alistair" <alistair@[EMAIL PROTECTED]
> wrote in message
news:69fe8ce3-c47d-44fd-bd02-8a0b5dc878d8@[EMAIL PROTECTED]
26 Feb, 20:36, "Pete Dashwood" <dashw...@[EMAIL PROTECTED]
>
wrote:
> "tim" <T...@[EMAIL PROTECTED]
> wrote in message
>
> news:13s728si8g08id9@[EMAIL PROTECTED]
>
>
>
>
>
> > On Tue, 26 Feb 2008 10:46:19 +1300, Pete Dashwood wrote:
>
>
>>http://www.wa****ngtonpost.com/wp-dyn/content/article/2008/02/23/AR200...
>
> >> What I'd like to know is exactly HOW you can establish yourself as a
> >> Geek,
> >> so you can claim this defence. If writing a file system for Linux is
> >> all
> >> it
> >> takes (a weekend's work for a COBOL programmer...), then there are a
> >> lot
> >> more Geeks around than many people may suppose.
>
> >> Did he do it? (Jo Brand, referring to O. J. Simpson: "Course he did
it;
> >> he's a bloke...")
>
> >> Thoughts?
>
> >> Pete.
>
> > You must be pretty good if you can write 15,000 lines of
> > multi-processing kernel code in a weekend.
>
> Well, leaving aside the fact that I AM pretty good :-), it was said with
> tongue-in-cheek...:-)
>
> As a matter of record, I once wrote a complete access method for a
> mainframe
> in a Bank, over a weekend. Another dedicated guy and myself worked on
> implementing it into about 300 programs over the same weekend. It
enabled
> direct access based on Account numbers and had its own ha****ng algorithm
> based around the structure of account numbers in that particular Bank.
It
> was a complete callable subsystem that implemented all the functions of
> data
> maintenance using VSAM RRDS. On Monday, everythng was working when the
> staff
> showed up. We had a total of 9 hours sleep each
As an aside, and not a dig, how long would it have taken under your
beloved C#?
[Pete]
Fair question.
Honestly? I have no idea.
If I was doing it in C# I'd probably use LINQ and SQL Server instead... I
don't know whether the FCL contains any kind of relative file adddressing
routines and I'm certainly not going looking :-)
I would readily admit that, at the time, COBOL was the perfect tool for
the
job.
Pete.
--
"I used to write COBOL...now I can do anything."
|
