Comments on: Technology's 10 most inexcusable failures
ZDNet's David Berlind has his dander up about half-baked technologies that still don't do what they're supposed to.
ZDNet's David Berlind has his dander up about half-baked technologies that still don't do what they're supposed to.
January 4, 2010 6:53 AM PST
January 4, 2010 6:42 AM PST
January 4, 2010 5:58 AM PST
Add headlines from CNET News to your homepage or feedreader.
More feeds available in our RSS feed index.
Related quotes
someone use MS Outlook? Why not? The fact is MS Outlook
should be good enough to use. There should not be these
problems.
Mangled String?
Mahogany Shelves?
Re: My Sandbox: Grow up, else crawl back into the hole from whence you came.
---Begin VBS File---
'Script to Paste/Navigate to URL after removing linefeeds
dim strURL, WshShell, objIE
set WshShell = WScript.CreateObject("WScript.Shell")
Set objIE = CreateObject("InternetExplorer.Application")
objIE.Navigate("about:blank")
strURL = objIE.document.parentWindow.clipboarddata.getData("text")
'Pull Out CRLFs
strURL=Replace(strURL,VBCRLF,VBNUL)
'Browse to fixed URL
objIE.Navigate(strURL)
objIE.Visible="true"
'Maximize IE Window (remove this line as desired)
WshShell.SendKeys("% x")
WScript.Quit
---End VBS File---
For those who are worried about a virus, read the code, understand the code, and point out what part does anything malicious... Then do the same for any EXE on your system and since you CAN'T see the code you won't be able to.
workarounds at all because there should be nothing to work
around.
Why do you expect people to know about these things? People
do exist that basically use their computer "as-is" because they
don't know how to change it or about what to change. Using a
computer "as-is" should work 100%, there shouldn't be these
problems that requires add-ons etc.
The cell phone carriers and manufacturers can provide so much more service and functionality if they wanted to...But they seem to be interested in bringing out new models that seems to have more hardware and no changes in the functionality...Hope manufacturers are read it and make these features available on all their cell phone models..
Caution: Do not hold breath waiting for change!
Back in Indiana, when they split area codes, we were notified that in 6 months, everywhere outside of the Indianapolis metro area was going to 765 from 317. Everyone made that transition.
But in Philly, they decided to keep the old area code and just add a new one. So people across the street from me in the new housing development are 484 and I'm on 610. Talk about confusion...
My feeling if you dial a number more than once, you put it in your cell phone phonebook. All 10 digits. Thank God its only 10 digits.
I can tell you, you will soon see the fruits of my labor and never again have fear of virus, software corruption, or lost data again. Right out of the box machine that will be as reliable as turning on the lights or water.
TJR
If OS/2 had succeeded, we would be light years ahead of where we are now. I like XP (with SP2), but IBM had many of the same features nearly 10 years ago!
To be fair to IBM, it wasn't all their fault. The hardware requirements (which are paltry to today's standards) were considered outrageous at the time. When most people only had 1-2 MB of RAM, OS/2 needed much more than that (was it 8MB?).
http://www.pc.ibm.com/us/think/thinkvantagetech/systemmigration/
Better yet, get an abacus. I'd rather use one than OS/2...
IBM has a history of brilliant ideas gone bad, like micro-channel architecture, java thin client workstations, and selling their PC business.
approached working with files from a
document-centric point of view, in which one
worked very much as one does in a real office:
You pick up a piece of paper and start writing
on it. It was brilliantly conceived as a total
object-oriented environment.
It was sooo obvious that M$ nicked a lot of the
bare concepts for their GUI from OS/2 without
the brilliant thinking and conceptualising
behind them, so that we're mired in the
patchwork hodgepodge that is Windoze XP
today.
I still feel that OS2 has plenty of strengths over Windows XP as far as stability and multi-tasking goes. My reason for using XP is the availability of software for it. IBM would do well to throw it out and let everyone have at it to tear it apart and build it from scratch. A true server OS that can run some Windows code!
The big problem is how much of the code they own, some of it was licensed to them by Microsoft who was a partner in the OS initial development that ditched IBM on the sidelines as soon as a new possibility came around.
The technology is there, you just have to pick the right vendor.
The first freakin VCR's 25 years ago that weighed 40 pounds didn't require grandma to bend behind the TV and unplug it when something went wrong! And even then the only thing that went wrong was a physical tape getting jammed or whatever.
They've eliminated the physical problems and added these electronic problems that are far more difficult to understand and deal with for the average user.
Another example before I post: portable music players! How many times has your player froze up trying to play a song? The old Walkman would either eat your tape or just keep on playing until the batteries died. Simple and user-friendly.
2. "95% right is good enough" This attitude seems to pervade every aspect of the computer world. If a vendor delivers 95% of what the sales demo promised, their job is done, right? Now multiply that scenario times dozens of vendors in a large shop and see how many buisness processes actually make it from start to end. Four nines should be the MINIMUM standard for completion of a project.
Of course, then there are the sales weenies constantly pushing for a new release, a new feature, something to sell their presentation, and to heck with whether it actually works or not....
"That's the nice thing about standards -- there's so many to choose from."
And if this doesn't suffice, try George Morrow:
"I believe in standards. Everybody should have one."
2: As a rule of thumb, every nine of reliability doubles the price, and you get what you pay for. The market determines what quality is tolerable, and if there were a market advantage to be gained by 99.9% quality, don't you think M$ would be using that to drive up prices (and associated stock valuations)?
1: The phrase "competing standards" seems destined to join "military intelligence" and "customer support" as infamous oxymorons.
We have software bios but still have 20 little connectors you need fingers the size of a gnat to be able to connect.
The author's choices seem to be little more than pet peaves about making his gadgets work. I wonder if he has heard the phrase "Get A Life".
Some of these things aren't bad ideas, but *top ten* failures of technology?
Talk about a misleading headline.
If I switched from Blockbuster to Hollywood Video, I wouldn't need a new DVD player.
I'd point out that a number of your issues are
solved simply by changing the applications you
use (for example, the address book and e-mail
issues). The problem for you is, how are you to
know that? Would you go as far as switching to
KDE on Linux if it solved your problem? The
answers are "you can't" and "probably not",
respectively.
Some of your complaints are functionality based.
You have a different opinion of how things
should work than the people that designed the
tool. That's to be expected because commercial
software is about profit maximization (aim for
largest available target demographic, minimize
development costs, increase margins, release
early, etc.). Commercial software will get the
majority of users the majority of the
functionality they want, and no more. If it's
not behaving right for you, chances are that
someone has written their own solution. The key
is to find it, and there's a good chance that
it: is open-source or shareware or Linux/UNIX
based, not well documented, and/or requires some
sort of semi-advanced knowledge to setup and
use. Finding something polished like Kontact
(KDE-based answer to Outlook, does most of the
things you ask) is fairly rare.
The problem isn't standards, either. There's
plenty of those. Standards are only adhered to
if the customer demands, unequivocably, that
they be. Why? Well, for the same reason there's
closed-source software. Conventional wisdom is
that if everyone agreed on how to do something,
you won't have a value added. Calendaring is a
good example. iCal is a standard that works
great and is widely supported in free-ware but
is largely ignored in the commercial
marketplace. Not that iCal can't do what the
user wants or the software is capable of, but
because if everyone used it, where would the
necessary product lock-in be to turn a profit?
The cell phone? There are all sorts of
regulations in the US that prevent a lot of
innovation there. Compound that with poorly
planned out networks, a multiplicity of
technologies, poor management, and an
environment where people are trying to figure
out why their phone has a video camera and an
MP3 player in it but can't make a simple phone
call with a stable connection and decent
reception. Why? US providers aim for phone
features over service because of long contracts,
and high cost of providing adequate service.
I will grant they should do a better job, however, but I seriously doubt you'll ever see the end of patches in our lifetime--well, unless we develop software that can correct its own bugs. :)
benefit whatsoever. It costs the country huge amounts of money
in confusion, besides the monumental effort of changing
millions of clocks. It's boneheaded stupid, and things only seem
to be getting worse.
The painful truth is that it does make economic sense.
And, to those who live a traditional nine-to-five working lifestyle, it *does* save daylight from their perspective. Who cares about the daylight you have while you're sleeping.
This also the reason it saves on energy costs. People don't have to turn on their lights for another hour, so that's an hour less they have them on at night.
Trust me, I wish there was no benefit to daylight savings time. That one 23-hour day really messes with my body's rhythm for the next few days; I'd rather not have it, either.
For me I use it to get 3 hours of biking in at the end of the day. And still get home with out having to deal with the boneheads in the cars tring to kill me in the dark.
I will admit when I was younger I did not understand it, and I hated it, now that I have a reall job (9 to 5) I see daylight savings as a great thing.
Unfortunately, he was talking to members of Congress at the time....and....well, some things haven't changed a bit!
There are a dozen ways to program around it, the best being to keep all data in Standard Time and convert just to display. This still costs money to change the clocks on the billions of displays. I have at least 10 clocks in my home counting clocks on computers, VCRs, oven range, stereos and alarm clocks and wrist watches. My wrist watch has a handy dandy feature to switch to "time 2" which is NOT set to the DST offset (I have it set to my "work time zone" that differs from the timezone I live in) resulting in having to change the time manually anyway.
To compound matters even more a company that spans the entire US market has to change clocks multiple different times in a wave effect over the nation. In an instant you can lose billions of cumulative hours.
If you want to save energy, just tell everyone to get up earlier! That's exactly what you are doing anyway. It's not that hard really. I work an 11PM to 7AM (midnight shift) but that's if I were on the East coast. So at 9:00PM it's 11:00PM to my "work clock".
I've been working in the tech industry for more than a decade and have never seen DST be a "non issue" anywhere I've worked. It is doubly troublesome for those who work during the time change.
- The cry of the masses..
- by April 12, 2005 1:27 PM PDT
- Ponder for a moment the real issue at hand here.. The people crying and complaining about these little issues are the people that have to have "everything" yet want to know nothing.
- Like this Reply to this comment
-
-
- Short-sighted
- by April 12, 2005 2:05 PM PDT
- Here's the problem.
- Like this
-
- Ignorant Idea
- by TV James April 14, 2005 3:21 PM PDT
- I wanted to start a whole T-Shirt company around ideas like this...
- Like this
-
Showing 1 of 4 pages (171 Comments)Heres a thought.. stop being the sheep and start being the wolf. Think about how stupid someone looks standing on the side of the road looking at their broken car or flat tire that they have no concept of how or why it works... they just want to get in and drive.. well guess what.. stupid is as stupid does..
You want a computer.. you want to store your important information on it.. grow up.. open your mind a little and learn WHY and HOW things do what they do.
Im sick of people crying about things they dont understand. Heres a quote that most intelligent people live by.. learn it.. live it.. and if your really smart.. you may even figure out where it came from.
"We can never see past the choices we don't understand"
Bob
If I learn my way around Outlook, that info is useless as soon as I move to another email product. Heck, it decays with every upgrade of Outlook itself! Ask yourself, how many packages can you be an expert in? How does a professional, whose real job is writing contracts, find the time to stay adept in three or four differnt software packages? Now what does that employee do when the company moves to a different product?
Once you learn how to drive a passenger vehicle, you can adapt to 95% of the cars on the road within an hour of use. Software companies had better wake up and start moving towards the same paradigm. The idea that it's acceptable to yank people out of the field and away from their primary buisness focus to train them to use products is going to go the way of the dinosaur.
If your product requires a three day class in order for an end-user to navigate comfortably, here's your sign. You have a problem.
"If everyone drove faster, we wouldn't have rush hour."
Your posit that if we all learned how the computers work, maybe we wouldn't have these gripes. That might work for the kinds of people we are, reading these posts. Wouldn't work for people like my wife or the 100 staff that my team supports.
We have a saying around here: "Don't Make Me Think." Comes from a really great book on web design: http://www.amazon.com/exec/obidos/tg/detail/-/0789723107/qid%3D1113517131/002-7251720-8145646
Basically, if you have to think, then we haven't done our jobs correctly in IT. Their job is to answer phones or run departments. Our job is to make sure they can send e-mail or view their boss' shared calendar. They shouldn't have to know why Microsoft asks them to do it a certain way. They just need to know that they can reliably expect it to work. And work the same way tomorrow that it did today.