Linearthe sloppy design of the file saving system (Microsoft Corp Sucks)
by A disgusted & frustrated Microsoft user 
, Monday, June 07, 2010, 03:30
I could never write a program, not even a simple one. Microsoft engineers have done a wonderful job of writing the code etc. However, because they are expert code writers does not mean that they think like lowly human being such as I. I for the life of me, I have the greatest difficulty avoiding having duplicates (or what at least appears to be duplicates to my lowly mind) when I save something.
Even worse, I have an extremely time consuming and frustrating experience trying to locate files after they are saved. Let the engineers stick to what they do best, and consult with us lowly common folks to learn how our minds work when we save and search for files. Let them write their programs not only so that they understand how to use the product, but with our input, construct it so that lowly common folks such as I can easily use it.
I would like to offer a comparison for the engineers to contemplate when they organize their product: Most people want a car that works in an intuitive fashion. They want to put the key in the ignition, turn it, put the car in drive and press the accelerator and go. When a software engineer is going home for the day, how would he feel about having to hunt for the ignition switch (or the correct combination of wires to twist together), experiment with how to put the car in gear, and then look for the accelerator pedal (or device)? (Maybe the accelerator could be semi hidden in the glove box. Maybe too, the headlights have to be turned on so that the electrical circuit to the ignition switch is completed.) Do you get the picture?
The feelings of annoyance that such an analogy arouse, are the same ones I feel when I use a non intuitive software product. Oh, by the way, having worked on cars for decades, I could easily design and build a complicated mess of a starting, gear selection, and acceleration system- that I would know how to use with no problem (just as the software engineers can easily maneuver through their sloppy product design.) Would a software engineer want to buy and operate a car such as the one I could build? Then why do they seem to think that a similarly non intuitive sloppy piece of software would appeal to me?
the sloppy design of the file saving system
Save things to your desktop, and stop whining. Are folders such as "Documents", "Music", "Videos", "Pictures" too difficult for you to wrap your brain around?
Really?
the sloppy design of the file saving system
The automotive "user interface" is not really intuitive. That's why you have to learn to drive a car. Many of the controls are standardized. Most cars have a steering wheel that turns the fromt wheels to the right when rotated in a clockwise direction and turns them to the left when rotated in a counter clockwise direction. most not have the gas pedal on the left the brake on the right and feature a key operated ignition switch on the steering column.
In the early days of automotive history, some cars used handlebars, some used steering wheels and a few used a tiller. Some used a hand-operated brake lever, some used a foot operated brake. Starters could be hand-wound recoil starters, or electric starts. in the latter case, the starter switch could be on the adsh, to either side of the steering control, and in some designs, the starter switch was on the started motor and operated through a foot pedal.
Even today, the gear shift may be in the floor, in a console, or on the steering column. The Plymouth Valiants on the early 60's used a set of pushbuttons in the dash to control the automatic transmission.
I have seen three different types of parking brakes, different placement of the lights and heater controls, different instrument cluster layouts. None of there are intuitive.
A gui using a mouse is not intuitive. A touch screen based GUI can be intuitive. But the problem with Microsofts user interfaces is inconsistency. A major point of frustratino in the Office 2007 line is the stupid ribbon interface. When you open a window in an application, you expect the minimise, maximise/restore and close controls to be in the corner of the window. You don't expect them to move off the window to another control when you maximize a widow.
There are dozens of these interface inconsistencies in Microsost products.
Try and make it short
this ain`t a news paper
Try and make it short
Its called reading. Sure its long but it has content, we can't all be "OH LOL MICROSOFT FAILS BECAUSE IT SUCKS LOL!" :/
