My new pet peeve - final

[Gary Wheeler]

Your attempt to put me into a state of maudlin sentimentality has succeeded, Ravi. Well played :-D. My last experience with a VAX was on a MicroVAX-II back in the late 80's. I worked for a defense contractor at the time. We developed simulations in FORTRAN and Ada. I also used the machine when I was taking graduate artificial intelligence classes. I *cough* borrowed *cough* a friend's C compiler and ported XLISP[^] from the IBM PC to the VAX.

Software Zen: delete this;

[Ravi Bhavnani]

Looks like we've walked similar paths. :) I met my first VAX in 1980 at school, and later in 1987 when I joined DEC's AI group.  There we used a bit of VAX Lisp, but mostly DEC OPS5 to build XCON[^]. /ravi

My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

[Gary Wheeler]

Ravi Bhavnani wrote:

There we used a bit of VAX Lisp, but mostly DEC OPS5 to build XCON

We talked about XCON in my AI classes. The opinion was that is was one of the first (if not the first) genuinely useful commercial AI applications. I seem to remember the professor saying there was a sign at DEC that said "Last year I couldn't even spell 'knowledge engineer', and now I R1." :cool:

Software Zen: delete this;

[Ravi Bhavnani]

Ha ha ha!  That was a quote from my boss, John (McDermott): "Three years ago I wanted to be a knowledge engineer, and today I are one." Throwback Tuesday[^] :) /ravi

My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

[Gary Wheeler]

Awesome. Think the youngsters are annoyed at the old farts and their war stories yet?

Software Zen: delete this;

[Ravi Bhavnani]

You're right. ^Z. :) /ravi

My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

[d shapiro]

Is it safe to say that this is your... final pet peeve?

[Lilith C]

I prefer to label mine with "Latest" since I don't know if it will be "final."

I'm not a programmer but I play one at the office

[sam silvercreek]

Which one is the final document? It must be the one named: document - REALLY FINAL - and we mean it this time.doc

[Glenn E Lanier II]

Simple: Newer. Next update: Newest Final update: Newester

[User 10798400]

For most documents I create and work on I name them like this: document.YYYY.MM.DD.docx Then I move older copies to a subfolder called archive. This has saved my bacon more than once. They also sort out quite nicely in windows explorer. I gave up long ago calling them final or rev 1 or rev 2, until actually officially released. I work in an engineering firm, and we do have an official document repository. When it's placed there it really is a certain version. then I can name my working file to correspond to the "publishe" official version.

Mike

[Mark_Wallace]

I've been known to produce documents like that, but I use a script that renames the files when a new version is added.

I wanna be a eunuchs developer! Pass me a bread knife!

[Chris Maunder]

Works perfectly if only one person is working on a document. Breaks down dangerously when two people are working on the same document. Which one is actually the final version and which one was merely saved last?

cheers Chris Maunder

[Bruce Patin]

I always add a letter to the date, starting with "a", so I don't have to deal with the time.

[StatementTerminator]

Give them credit, if a marketing schmuck can run the most powerful tech company in the world into the ground there's no limit to what they can do! Back on topic, make a shared Google doc and let the drones fight amongst themselves.

[Stefan_Lang]

You're doing it wrong - the only signature that counts is the client's! ;P

GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

[Stefan_Lang]

What about the updates after the final one? E. g. New Final Newer Final Newest Final :cool:

GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

[Stefan_Lang]

Nah - makes too much sense! We'll never get management to accept that! ;P

GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

[Stefan_Lang]

AFAIK that's only meant to compare the most recent (or FINAL? ;P ) changes. I doubt it can track revisions of revisions. I remember using such a feature in document reviews some 20 years ago. Of course version control was rudimentary at the time, and nobody ever thought of versioning word documents either, so what we did is maintain version numbers right within the document. At least that kept the confusion concerning names to a minimum. But it had other drawbacks... :^)

GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

[Stefan_Lang]

I'd prefer "The most recent final at the time of this writing" :cool:

GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)