I looked at PowerShell. It makes me no sense.

Unix and REXX grew up based on things that people actually needed, rather than dictated ex citidel. To this end, once one has a UI (in the form of STDIO), it's easy to write stream filters. I write quickies for this in REXX. Strongly typing means that you can only treat a file name as a file name, rather than say, a string. It also means that you can't add 1 and 1..

Still, those of us who have lives in the real world do fine-tune things with a spanner etc, such as to give some more gain to the victa or level the fridge. So the notion of a spanner and screw-driver for configure (ie adjust), has still some sense. Also, there's the delightful phrase 'spanner in the works'. This is just the dandy place to do it (i recall one girl changing all of the window furniture to blue, and then wondered why she couldn't see anything!).

One should remember that the hard disk icon is sometimes shown as a stack of platters, and sometines as a grey box, but in one instance, the hard drive is not the volume, and secondly, not many people would pick out the fixed disks in a beige box. It's also interesting to see what people would think of floppy-disk icons when floppies aren't allowed at work.

Still, there are steam engines used to show level crossings, because of all things railway, the steam engine is perfectly recognisable.

As to the rabbit ears on the tele, that's about the most distinct thing about it, and even TiVo uses it in their logo.

I used to have a real teletype behind me at work, to do queries. The thing would chug into life every now and then with the answer to some command entered into a computer. One would type in a card line (rather like command options in the cobol style), and it would send back a string of lines.

The joys of the card punch and the tape punch. These chug away, likewise mounted so that their vibrations would not do some damage.

The sound of bells relaying messages, when BEL actually rang a bell. Of course there (was) the telephone system i saw my brother use, to ring up control at roma, consists of a party-line system, where one rings long-long-long etc.

Here (australia), it was the custom to play the national anthem (god save the queen), at the end of every show (cinema, live, television close). In the seventies, they changed it to some other thing (advance australia fair). One day not too long ago, i was listening to a disk of national anthems, and found that i was standing when GSTQ was played. So ingrained. (They used GSTQ to get the beatles out of an adelaide theatre: the beatles made their exit as the audience stood at attention to higher things).

Real money. not a sound, but the cash registers and so forth were generally mechanical things where one might press the money in and pull a lever. Australia abandoned currency on 14 feb 1966, when we got these decimal beads in.

The real thing with e-mail etc is that one ought treat it as an electronic inbox, and not something to dance to every beck and call.

One works on a variety of tasks, rifling the inbox for the next task. It's the same with inbox stuff. You might assess incoming tasks for urgency and importance, but if you jumped to every task as it hits the desk, ye'd never get nothing done.

It should be remembered that efficency and effectiveness generally are unrelated.

Efficiency is something that can be measured: responces to calls, forms processed, etc, the sort of thing you can count. It's pretty easy to do this sort of thing, and often the PHBs will take some metric and use it as a measure of activity. Because of this, one often sees things like proformance indicators, and the process and often salary, becomes connected to the indicator. The industry stops being what it is and starts producing 'red beans' for the bean counters. The indicator changes, and one produces blue beans.

Effect is something that is about getting the right job done, both for the customer and for the system. It's not even about what the customer wants, since this supposes that it is the role of the customer to diagnose the problem and the solution, and simply ask for the solution to happen. One needs to think of what happened with the system that responded to cyclone Katrina in New Orleans, which the responce was based on customer wants, rather than pre-assessment by those who should have done this. A call for help is an indicator to a problem, not a proposed solution.

Of course, even though an indicator might be proportional to effect in the wild, when it is proportional to money, the indicator becomes more important to the effect. A doctor, who might have an indicator on consultations, will split several illnesses to several consultations. On a help desk, one is more intent on creating calls, then on providing effect. A call that seeks three problems would be terminated at the first, and new calls needed for the second and third. Also, the process might be extended to several calls to create extra indicator traffic.

In the main, help desk traffic is not a really good indicator of effect, since there are things that effect this. Response time, time to fix, etc, all serve to alter traffic, in some cases, it might be better served by the section guru rather than the help desk. The effectiveness of the guru's solutions may well impede the help desk's overall issues, since it might make matters worse.

One should also note that recording the help calls is also an impediment. It serves no effect, and in many cases, might take as much to make happen as the call does in nature. One might answer say, 90% of the calls first up, yet spend more than 50% of the times making the necessary beans for the counter. A good deal of issues can be condensed into a few batch files (yes, i did this: system configuration is a good candidate for script files), so that while the call is terminated relatively fast, the actual recording might be tedious.

My experience of help desk is that particularly Microsoft rograms (eg Word, Access, Windows), use common names, which makes them very hard to grep for in the system. This reduces the effectiveness of any sort of 'search the job tables' for help. To this end, i used Wart, Abcess, Windoze, much to the annoyances of the PHBs.

Still print because my copy of vproof (proof-reader proggie) does not really work on the screen.

I make use of style sheets as much as possible. This allows for example, either block or first-line indent. With a style-sheet set down to character-level, one can use single or double-spaces freely at the end of a sentence. The markup language I wrote (KML, see, eg http://www.os2fan2.com/ makes use of a chacter-level style sheet that replaces eg `t and `T by th,TH or , respectively, eg 'the polygloss' vs 'the polygloss as nature intended', both derive from the same source KML file.

One uses also two kinds of paragraph (p) and (pp), to create leading vs following paragraph. The pp-style paragraph can have either first-line indent (traditional) vs blank-line block style.

Don Knuth described Literate Programming in which the program is embedded in comments, one using a preprocessor to write the program. The preprocessor runs as a command processor, using the source as a batch file. One gets a properly sorted batch file as output. Because of this, one can overcome limitations of the programming language, use pre-processor variables etc, and produce several linked files etc.

Documentation is relatively straight forward, since one writes what one wants to get, limitations, API and examples by way of a wish-list, and then create the routines that make this happen. You can write a tight section like "File I/O", for fileopen() and fileclose() along with getline(), putline(), etc, without exposing the filenames to all of the subroutines. I've written a program to write Web pages in it, for example, http:\\www.os2fan2.com\pgloss\index.html and its attendent pages. It's pretty elegant really.

The temptation of LP is to use it to solve a problem per source, a note that Jon Bentley (Pearls of Programming) noted. LP is about sorting problems: however, the sort of problems that Knuth sought to solve are complete things in an educational setting, not bits of problems in the real world. None the less, I use it to write terse batch files etc, where the LP source is the help file too.

Two tricks i use to hide passwords is to use short forms, eg "A7" might expand as "ABD968017", and a general "salt and pepper" table. These are all unrelated to what is typically discussed. Note also that a7 expands to "abd968017", so some case can be preserved.

In a salt and pepper table, one uses an intermediate table that is easy to recall, but no need to be written, and not common knowledge. An example might be "husbands and wives", so a password displayed as "John" might be entered as "Yoko". Another kind of table might be "middle names", so "John" would elicit the response of "Winston". Note eg, jOhn gives yOko or wInston, so you can hide case in here too.

The less obvious you make the salt and pepper table, or the more unobvious the abbreviations, the more secure the table, even if the reminders are kept in plain text (plain text in an unobvious application also deters automatic gathering. Who would look for something like a .DOC file, might have some fun when the downloaded document is a multimate doc!

It's interesting that the bulk of the SxS stuff is Microsoft stuff, not third party stuff.

I recall that when Win95 first came out, and that they were replacing the Win16 stuff with Win32 stuff. Someone remarked that there would be incompatibilities, and that it was for the vendor to rewrite the apps to meet the new APIs. That calling some DLL by name would of course these incompatibilities.

I thought how silly. Inviting third parties to use routines in your DLL is pretty much a kind of contract of support. This is the nature of the operating system, really. If you create a DLL like VBRUN100 for some set of apps to call, then the App expects it to run in that way, and if your new version of VBRUN would cause incompatibility, you should give it a different name, like VBRUN200.

Last time i looked, routines like VBRUN100, BWCC etc, comes to about 9 MB. (There's a download that ye can add to your OS to give these as preinstalled.

Where the problem comes is when some sort of obvious name gets used for different DLLs (eg the three different versions of THREED.VXD that different applications were loading under Win31), or the MFC3xx DLLs where the source code was given to vendors to allow them to add their own functions. (good lord). Even so, Microsoft continues to release DLLs like MSVCRT and MFC40, updated to their latest operating system / compiler.

I don't think anyone else uses such nonsense as SxS or DLL hell: OS/2 VREXX.DLL or EMXRT do the right thing: preserve existing functions, and have a test for version-level.