"Nor" is a hangover from Old English, when the language had a dual number in addition to the singular and plural we have today.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
I am flying from Australia to South America for a holiday. Because of all this TSA nonsense, I paid extra to fly via Chile rather than USA. This also means I flew using LAN rather than a USA airline (which is money lost for the USA economy).
That's odd. I would think Australia to South America would require WAN, not LAN
I think you are confusing LAN meaning "Local Area Network". WAN means "Wide Area NetworK", but it's not so much wide as it is long. Hence in this context LAN means "Long Area Network"
- Security (they want equivalent of Australian "Protected" or USA "Confidential").
- Secure wireless distribution of meeting documents to tablet devices.
- A secure collaboration space so that staff in separate offices can work together on developing documents for the meetings.
I'm keen to get a feel for what sort of products are on the market and how well they work. What are your experiences with secure meeting management / document collaboration and distribution systems?
Everybody seems to be confusing the term "customer" with "stakeholder". The fact that a person may not understand what they really need when asking for an info system should be no surprise to anyone in the IT industry by now. It's the whole reason for the existence of business analysts like me. Being a good programmer does not by any means guarantee that you are good at gathering and understanding requirements. Being a good BA certainly doesn't make me any sort of programmer (though I do understand the concepts).
And the customer is not always synonymous with user. The role of the BA is important, but it should be part of facilitating communication between the developer and the user, not a firewall keeping them apart.
That depends on both the developer and the user
I deal with some users that have almost no clue about computers and technology, so they have a tendency to think that IT development can deliver more than it can in a lot less time than it really takes. Even worse, the organisation I work in is strongly hierarchical so my communication with some users is often via several layers of management (each of whom know very little about computers and technology). Suffice to say, it is quite the challenge to manage users' expectations!
I don't understand that argument. If there was an emergency that required evacuation, you would have to be pretty darn absorbed in your game not to notice the bumping and the oxygen masks coming down and the smoke and the people screaming and the loud "assume brace position" warnings. The time it takes to put your Game Boy down is probably significantly less than the time it would take to undo your seatbelt, stand up and get into the aisle of a plane full of other people all trying to get off as quickly as they can.
Also - copyright terminates when the author(s) die. None of this life-plus-eleventy-thousand-years crap. When you kick, your works revert into the public domain
Except the author when something horrible happens to him/her because they are in possession of a multi-million dollar copyrighted work that others would like to exploit...
The business representative should be handed a business requirements document, written by a decent business analyst, that clearly explains to them in words they understand exactly what the system will do.
It's wrong to expect someone to sign off on a document they don't understand, and whilst it may achieve the goal of deflecting accountability, it won't result in a good product.