Re: command line arguements with spaces in them
- From: gordonb.nutvd@xxxxxxxxxxx (Gordon Burditt)
- Date: Mon, 17 Jul 2006 06:09:52 -0000
FooReport20060714.tex
Makes my point, quite frankly. This is vaguely readable, but only if
you already know the topic.
Project name, indication that it's a report, date, file extension. And,
quite frankly, all of the above is unnecessary.
I disagree if there's any chance copies of the report would be emailed
around or distributed outside the company LAN. Some of the details
might be moved into the directory name but spreading stuff out over
many directories just makes it harder to find stuff.
The report would be stored
in the Foo project's part of the server, in a "WeeklyReports" section, and
the filestamp carries the date.
This isn't necessarily true while the report is being prepared (when
it's probably on the personal workstation of the person preparing
it), or for backups of that server, or if someone takes the report
home to work on (and doesn't have direct access to company servers
from the Internet at large, which is probably a good thing).
It's unrealistic to assume that the "server for the Foo project" will
never change (for example, because it needs more space or horsepower)
or that backups of the old server will be re-done to move the files
to backups of the new server.
It also doesn't deal with the issue that each person working on the
Foo project may prepare their own report (so there are lots of
weekly reports for a given week), which is combined by the project
leader/manager into an overall status report for upper management
(and which perhaps should not be visible to project members), which
may go further up the chain.
The filestamp carries the date it was modified, *NOT* the period the
report is for. This is an important distinction, since reports
can be written early or late, and can be retroactively modified.
Even the file extension is unnecessary,
since the nature of the file is evident to anyone who reads it.
Really? Windows doesn't seem to think so. The UNIX "file" program
is rather clunky and doesn't always unambiguously figure out what
kind of file it is. And you expect people "reading" it to figure
this out how?
The only
necessary name would be: <serialnumber>
For those who need wordy descriptions, it may well be that an indexing
document meets their needs nicely.
seventy letters of complaint to your bank
BankAddrChangeDispute/bacd19930513.tex
BankAddrChangeDispute/bacd19930604.tex
Indeed, well and truly hammered home. This is just plain unreadable.
Really? I disagree, but readability is in the eye of the beholder, is it
not?
Gordon L. Burditt
.
- Follow-Ups:
- Re: command line arguements with spaces in them
- From: Richard Heathfield
- Re: command line arguements with spaces in them
- References:
- command line arguements with spaces in them
- From: raphfrk
- Re: command line arguements with spaces in them
- From: Richard Heathfield
- Re: command line arguements with spaces in them
- From: Mark McIntyre
- Re: command line arguements with spaces in them
- From: Richard Heathfield
- command line arguements with spaces in them
- Prev by Date: Re: command line arguements with spaces in them
- Next by Date: beginner level question
- Previous by thread: Re: command line arguements with spaces in them
- Next by thread: Re: command line arguements with spaces in them
- Index(es):
Relevant Pages
|