"How do you make sure the most current changes in a file aren't overwritten? How do you audit the changes made; when they were made and who made them? How are you supposed to know what changes were made?"
Oh gosh I think Mainsoft must be burying their face in their hands...
"Developers will also appreciate Visual MainWin's J2EE Integration Package and industry-leading XML support. And it actually recompiles Windows source code with the Unix compilers to create native Unix applications..."
Speaking from experience with H-1B contactors and L-1s working in the U.S., the cost savings these companies seem to "realize" for I/T is not as rosy as one would think. Most managers that make these decisions can barely understand a balance sheet and an income statement, but they can certainly read a stock price. When outsourcing looks like an option, you have to look at all the hidden costs that lurk about doing it before you dive in.
Unlike unkilled and semi-skilled manufacturing jobs, where the tasks performed are route and routine, a lot of programming jobs require heavy amounts of cooperating and coordinating to get a successfull result. The proper analogy to draw with your client is that of the homebuilder/architect and the homebuyer. Although the programmers may be Mexican immigrants who work less than minimum wage and get paid cash under the table to send to their poor families in Guadalajara, these folks still need the same amount of (if not more) specific direction to build a home that will be fit for you and your family to live in. Translating back to I/T, you may be mired in many, many more meetings, buried in email, and endless phone calls with your overseas colleages just to keep the train on its tracks and moving in the right direction. Be careful what you outsource.
Ever heard the old addage "too much of anything is not a good thing?" Same principle here. A proper mix of outsourced labor and internal I/T staff can build successfull solutions with less cost than the tranditional MIS department (in less time is another story). Some jobs are perfectly suited to be outsourced, such as the DBA, data-warehouse specialists and some of the programming. The traditional PC helpdesk has also been successfully outsourced overseas, but you better hope that your callers can tolerate the Bombay accent on the other end of the phone.
Some jobs cannot be outsourced without expecting a downturn in quality or a corresponding increase in time spent doing your project, such as technical writing, quality assurance, project and program management and many other jobs that require intense amounts of personal and communication skills. Hardware, network and software installs should NEVER be done by outsourced personnel. You also want to keep the programmers who are working on the big things, such as architecture shifts and regulatory changes (e.g. HIPAA) on staff for the tight projects where you don't have the luxury of time on your side.
Outsourcing CAN be done, without firing your entire I/T staff, alienating everybody and stirring up bad blood. Find jobs for the folks who are being placed out or train them to do the jobs you aren't sending out of the company.
And even when you get to the state where you can do offshore and realize a gain, you still have to keep busy monitoring everything much more vigilantly. Outsourcing companies charge vastly different prices for the same tasks, and contracts don't span very long. There is also the question about what happens to your intellectual property when it's going out of your country's borders: if you are compromised from an overseas vendor you may be left with little or no recourse (which is why so many CEOs are lobbying Congress). The cost of securing a favorable contract with an overseas parter also adds to the cost, unless you are doing it through a U.S. firm (but don't think that those international legal firms' fees WON'T be passed down to YOU). I doubt that most PHBs will get outsourcing done right without paying a large sum of dough to outsourcing specialists (hmm maybe a new career option to layed off I/T workers?).
Where does this experience come from, you ask? Well, I was replaced by Indians several years ago, which then followed up with a massive layoff at the company I used to work for. They are paying less money for the labor, but since I left they have had more projects fail miserably than before. They may have let off with benes and pension plans, but they traded it in for huge sums of airline fees to sh
800,000 machines. Let's assume $125.00 US for the OS and $295.00 US for Office. That's $420.00 US.
So, we're talking about $336,000,000 going to Microsoft just for the basic OS and Office productivity software. This doesn't include all the money spent on Microsoft Premier Support, servers and the army of consultants required to support it all.
If you can keep the headcount stable, refactor most of your critical desktop apps to Java, and swap out the OS to something with a much cheaper license fee you could save a bundle and even have room to a) hire better-skilled I/T staff and b) provide better user support to offset the transition.
Not every OS changeover is an OMG-We-Are-Going-To-Die situation. I've lived through 8 OS changes in 4 different companies and everything came out fine in the wash.
I know of a particular BIG insurance company here in Texas that outsources a LOT of their core work overseas. This company happens to cater to members of the US armed forces and civil service employees. When people get deployed or move, they have to call this company to have all their addresses changed.
To think... now India and Pakistan probably now have a good listing of where a lot of our US service members are located. It's glad that India and Pakistan are our "aliies" or we'd really be in the shit now...
Yeah, see... we pass laws like HIPPA... pay Indian programmers to modify millions of lines of C code running on old VAXen and HPUX boxes and other antiquated garbage medical firms run and standardize on a common set of EDI transaction codes (837/835s, etc)... and now there are huge villages of people near Bangalore that have access to everybody's business over the Internet. I'm sure we can pass more laws that will be "enforced" on the backs of Indian labor.
I've worked in several very large organizations. Here's a short list of tacticts to use to thwart ever-increasing boosts in workloads:
- Use program management. Program management is different than project management, in where you prioritize projects based on needs by the business, and effort is directed to the ones that provide the most bang for the buck to the business.
- Competing interests. If you have unreasonable requests from non-revenue generating departments, put these people in front of the executives (call an emergency meeting) who are running the revenue-generating part of the business and have them explain why you have to work 200 on some boss's Crystal report versus fixing a production problem that is affecting sales. Works everytime.
- Be more visible. The more people know what you are working on and what your backlog is, the requests that come in will be thought-out a lot more often if the business thing all you do is eat pizza and read/.
- Use cost-analysis studies. Spending 6 hours to write up a white paper exploring your users' idea and the pros and cons may save you hundreds of hours of work having to do the request (especially if the business decides it's a bad idea later on). The thicker the document is, the more the business is inclined to think that you have approached the idea and its implications than if you merely shot off an email saying "we're too busy to do that" or, "that's a bad idea."
- Face time. Meetings suck, but you should at least go to one to two of them a day and stay involved, especially the meetings where the businesses cook up new ideas that impact the I/T department. Meetings are usually were the business cooks up these requests, so you can snub them out at the source, or redirect their brainstorms into better projects that will be more useful to the organization.
- Use the business process against itself. Larger organizations typically have a project management process they use. A lot of projects die while still in the design stage. Typically this is because the business gets distracted with another pressing matter and the project seems much less urgent after enough time passes. If you need a lot of time to work on construction on some other effort, you can usually effectively delay the construction on a new project by stretching out the design phase (call lots of review meetings). It looks like you are working on the project, but you aren't actually building anything.
There are a lot of other options for tanking projects, I've used various techniques to get rid of some really bad ones... but these are the ones I use most often and have served me well.:-)
My company (The SCOOTER Store) manufactures an inexpensive scooter that doesn't cost an arm and a leg ($999) to use, has accessories, and you can sit down in the thing and go several miles in it, and it folds up and fits in your truck.
We also sell the traditional stuff (scooters and power chairs) directed at Medicare recipients and those with private insurance who need it to improve their mobility. The PTVs are designed for more everyday outdoor use.
They would be perfect for NOC employees who have to move around from terminal to terminal all the time...:-)
I was faced with this very same problem; and it's actually worse because at my workplace we are actually allowed to drink beer at OUR DESKS (on special occasions, of course). At my heaviest, I was 235lbs with a 41"w. Now I am 157 with a 31"w.
When you work with a department of over 150 people with company sponsored birthdays and anniversary confections, lots of deadlines, late nights, no time to do sports, etc... the waistlines tend to bulge.
How I approched this problem: running. And lots of it. Cardio exercise early in the morning before you eat draws energy away from stored fat (think about it, you haven't eaten for at least six hours... where else are you going to make ATP from?).
It all depends on your weight, ability to withstand hard impact (running is very hard on your ankles and knee joints), and ability to keep a steady pace (5.0mph-6.0mph is a very good clip).
For most people, a treadmill or running outside with a pedometer for 1 mile in the morning every other day, after you have woken up, works.
Don't eat until after an hour after you have worked out. If you can't do this in the morning, then wait 3.5-4 hours after you have eaten at night (although it's not as effective as running in the morning).
After you start dropping some weight, start a weight training program. Increased muscle mass will cause your body to draw even more calories for fuel, and it will boost your metabolism.
As far as dieting goes, it's ALL crap. Low-carb, high-fat, all of it. You cannot get around not exercising. For myself, I boosted the amount of veggies I eat to where it's over half of my diet. Pizza, chinese and mexican has to wait til Sunday when I'm not exercise.
Replace the soda you are drinking with water (soda makes you retain water like hell). If you can't stop glugging that Mountain Dew, force yourself to drink a bottle of water for every cola you down. Vending machines are evil.
There are also other things you can do to get the weight to come off and stay off... find things to do other than slave yourself to the computer! I took up skydiving (yes, I know, not for everyone). Find outdoorsy stuff to do.
Okay... so everytime a pay batch is run the server is going to do a bunch of GDI graphics drawing? I don't think so.
The fact that when you launch a Windows server a GUI comes up doesn't mean that the GUI is going to sit there and drain a huge amount of resources against whatever business process you having running on the server (unless the batch is doing some GDI work, such as stamping logos on paychecks or spraying barcodes or some silliness like that).
The argument of "well, you can run Linux with no GUI" is really lost on me. The Linux box is probably going to be running web services or servlets anyway... having an idle X session on the box is no different than having an idle explorer.exe process running on a Windows machine.
Politicians here have to spend lots to get the dead to vote... but they manage to turn out year after year. How failful to their citizenry after they're gone...
McBride, who is fluent in Japanese, will visit with several founding members...
Translation?
HI MY CODE MAKE YOW AIX GO SUCKY-SUCKY. I FILE IP SUIT, YOUR COMPANY GO **BOOM!***
Let me see: Tapping a phone line is not an invasion of privacy but capturing the electromagnetic waves that pass through my body IS? This is not a technologically logical argument here.
Had the FBI broken into the home and tapped the machine, THAT would have been an invasion of privacy. Had the FBI planted a trojan horse on his computer, THAT would have been an invasion of privacy.
Face it, this technology has been out for years. The guy should have known and/or shielded his computer, pure and simple.
1. Click Start, Settings, Control Panel.
2. Click Add/Remove Programs
3. Select Outlook Express
4. Click Remove or Uninstall (depending on OS version).
5. Go get a copy of Pine compiled for Win32 and install it ASAUC (As soon as you can).
This was first proposed after Voyager I and II flew past the planet and took high-resolution pictures of Europa's surface. Since then, it has been touted as a possibility from non-scientists like Issac Asimov all the way into movies (a.k.a. 2010 A Space Odyssey).
If there is any life to be found, it's probably some awful mold that any ordinary domestic scientist would promptly kill with Lysol.
Most speakers at last week's NetMedia'2000 conference in London proclaimed WAP a temporary aberration that delivers substandard services.
British and continental newspapers are full of stories about WAP phones that don't work and services that are difficult to use.
Many commentators point out the simple fact that since you have a phone in your hand, most tasks are faster to perform by simply placing a voice telephone call than by using WAP.
Things have changed greatly:
October 1999:
I was a rather lonely voice when I called WAP the Wrong Approach to Portability in my October 1999 Alertbox.
Most other commentators were very keen on WAP during 1999 when the hype was in full gear.
April 2000:
As recent as during my last trip to Europe in April 2000, most people had great expectations for WAP. Cooler heads who had conducted initial usability studies of the first WAP phones did raise a few concerns in April 2000, but the received wisdom was still in favor of WAP just a few months ago.
May-June 2000:
The picture started changing and the first negative reviews were published in European newspapers that had tried WAP services and pronounced them useless.
July 2000:
A new consensus has now been reached: nobody predicts great things for WAP any more. The excitement has shifted to:
Future mobile services with bigger screens and faster, always-on connections (except for the British telecom company Orange which cluelessly supports a technology called HSCSD with an unpleasant need to dial up every time anything is downloaded).
The Japanese I-mode system which is superior to WAP as a current-generation service.
Seems like WAP was already doomed last year. The Brits and euro web developers were already shunning WAP last year.
I can still remember the system architects at work drumming up white papers to convice an outpouring of cash into R&D for WAP but it never quite got anywhere. Who has the time to drive (late) to work and do their makeup and hair much less key 4445533111229955 on their cell for the favorite stock quote?
Slashdot Mirror
"How do you make sure the most current changes in a file aren't overwritten? How do you audit the changes made; when they were made and who made them? How are you supposed to know what changes were made?"
Oh gosh I think Mainsoft must be burying their face in their hands...
"Developers will also appreciate Visual MainWin's J2EE Integration Package and industry-leading XML support. And it actually recompiles Windows source code with the Unix compilers to create native Unix applications..."
Oh how true Mainsoft's marketing is...
Speaking from experience with H-1B contactors and L-1s working in the U.S., the cost savings these companies seem to "realize" for I/T is not as rosy as one would think. Most managers that make these decisions can barely understand a balance sheet and an income statement, but they can certainly read a stock price. When outsourcing looks like an option, you have to look at all the hidden costs that lurk about doing it before you dive in.
Unlike unkilled and semi-skilled manufacturing jobs, where the tasks performed are route and routine, a lot of programming jobs require heavy amounts of cooperating and coordinating to get a successfull result. The proper analogy to draw with your client is that of the homebuilder/architect and the homebuyer. Although the programmers may be Mexican immigrants who work less than minimum wage and get paid cash under the table to send to their poor families in Guadalajara, these folks still need the same amount of (if not more) specific direction to build a home that will be fit for you and your family to live in. Translating back to I/T, you may be mired in many, many more meetings, buried in email, and endless phone calls with your overseas colleages just to keep the train on its tracks and moving in the right direction. Be careful what you outsource.
Ever heard the old addage "too much of anything is not a good thing?" Same principle here. A proper mix of outsourced labor and internal I/T staff can build successfull solutions with less cost than the tranditional MIS department (in less time is another story). Some jobs are perfectly suited to be outsourced, such as the DBA, data-warehouse specialists and some of the programming. The traditional PC helpdesk has also been successfully outsourced overseas, but you better hope that your callers can tolerate the Bombay accent on the other end of the phone.
Some jobs cannot be outsourced without expecting a downturn in quality or a corresponding increase in time spent doing your project, such as technical writing, quality assurance, project and program management and many other jobs that require intense amounts of personal and communication skills. Hardware, network and software installs should NEVER be done by outsourced personnel. You also want to keep the programmers who are working on the big things, such as architecture shifts and regulatory changes (e.g. HIPAA) on staff for the tight projects where you don't have the luxury of time on your side.
Outsourcing CAN be done, without firing your entire I/T staff, alienating everybody and stirring up bad blood. Find jobs for the folks who are being placed out or train them to do the jobs you aren't sending out of the company.
And even when you get to the state where you can do offshore and realize a gain, you still have to keep busy monitoring everything much more vigilantly. Outsourcing companies charge vastly different prices for the same tasks, and contracts don't span very long. There is also the question about what happens to your intellectual property when it's going out of your country's borders: if you are compromised from an overseas vendor you may be left with little or no recourse (which is why so many CEOs are lobbying Congress). The cost of securing a favorable contract with an overseas parter also adds to the cost, unless you are doing it through a U.S. firm (but don't think that those international legal firms' fees WON'T be passed down to YOU). I doubt that most PHBs will get outsourcing done right without paying a large sum of dough to outsourcing specialists (hmm maybe a new career option to layed off I/T workers?).
Where does this experience come from, you ask? Well, I was replaced by Indians several years ago, which then followed up with a massive layoff at the company I used to work for. They are paying less money for the labor, but since I left they have had more projects fail miserably than before. They may have let off with benes and pension plans, but they traded it in for huge sums of airline fees to sh
Okay.
800,000 machines. Let's assume $125.00 US for the OS and $295.00 US for Office. That's $420.00 US.
So, we're talking about $336,000,000 going to Microsoft just for the basic OS and Office productivity software. This doesn't include all the money spent on Microsoft Premier Support, servers and the army of consultants required to support it all.
If you can keep the headcount stable, refactor most of your critical desktop apps to Java, and swap out the OS to something with a much cheaper license fee you could save a bundle and even have room to a) hire better-skilled I/T staff and b) provide better user support to offset the transition.
Not every OS changeover is an OMG-We-Are-Going-To-Die situation. I've lived through 8 OS changes in 4 different companies and everything came out fine in the wash.
I know of a particular BIG insurance company here in Texas that outsources a LOT of their core work overseas. This company happens to cater to members of the US armed forces and civil service employees. When people get deployed or move, they have to call this company to have all their addresses changed.
To think... now India and Pakistan probably now have a good listing of where a lot of our US service members are located. It's glad that India and Pakistan are our "aliies" or we'd really be in the shit now...
Yeah, see... we pass laws like HIPPA... pay Indian programmers to modify millions of lines of C code running on old VAXen and HPUX boxes and other antiquated garbage medical firms run and standardize on a common set of EDI transaction codes (837/835s, etc)... and now there are huge villages of people near Bangalore that have access to everybody's business over the Internet. I'm sure we can pass more laws that will be "enforced" on the backs of Indian labor.
I tried searching for "Crack Dealers" in "Dallas, TX" and couldn't find any. Oh well.
So it would be illegal to distribute and use gcc / Delphi / Watcom C, and the other development tools hackers love to use?
I've worked in several very large organizations. Here's a short list of tacticts to use to thwart ever-increasing boosts in workloads:
/.
:-)
- Use program management. Program management is different than project management, in where you prioritize projects based on needs by the business, and effort is directed to the ones that provide the most bang for the buck to the business.
- Competing interests. If you have unreasonable requests from non-revenue generating departments, put these people in front of the executives (call an emergency meeting) who are running the revenue-generating part of the business and have them explain why you have to work 200 on some boss's Crystal report versus fixing a production problem that is affecting sales. Works everytime.
- Be more visible. The more people know what you are working on and what your backlog is, the requests that come in will be thought-out a lot more often if the business thing all you do is eat pizza and read
- Use cost-analysis studies. Spending 6 hours to write up a white paper exploring your users' idea and the pros and cons may save you hundreds of hours of work having to do the request (especially if the business decides it's a bad idea later on). The thicker the document is, the more the business is inclined to think that you have approached the idea and its implications than if you merely shot off an email saying "we're too busy to do that" or, "that's a bad idea."
- Face time. Meetings suck, but you should at least go to one to two of them a day and stay involved, especially the meetings where the businesses cook up new ideas that impact the I/T department. Meetings are usually were the business cooks up these requests, so you can snub them out at the source, or redirect their brainstorms into better projects that will be more useful to the organization.
- Use the business process against itself. Larger organizations typically have a project management process they use. A lot of projects die while still in the design stage. Typically this is because the business gets distracted with another pressing matter and the project seems much less urgent after enough time passes. If you need a lot of time to work on construction on some other effort, you can usually effectively delay the construction on a new project by stretching out the design phase (call lots of review meetings). It looks like you are working on the project, but you aren't actually building anything.
There are a lot of other options for tanking projects, I've used various techniques to get rid of some really bad ones... but these are the ones I use most often and have served me well.
Good luck.
My company (The SCOOTER Store) manufactures an inexpensive scooter that doesn't cost an arm and a leg ($999) to use, has accessories, and you can sit down in the thing and go several miles in it, and it folds up and fits in your truck. We also sell the traditional stuff (scooters and power chairs) directed at Medicare recipients and those with private insurance who need it to improve their mobility. The PTVs are designed for more everyday outdoor use. They would be perfect for NOC employees who have to move around from terminal to terminal all the time... :-)
I was faced with this very same problem; and it's actually worse because at my workplace we are actually allowed to drink beer at OUR DESKS (on special occasions, of course). At my heaviest, I was 235lbs with a 41"w. Now I am 157 with a 31"w.
When you work with a department of over 150 people with company sponsored birthdays and anniversary confections, lots of deadlines, late nights, no time to do sports, etc... the waistlines tend to bulge.
How I approched this problem: running. And lots of it. Cardio exercise early in the morning before you eat draws energy away from stored fat (think about it, you haven't eaten for at least six hours... where else are you going to make ATP from?).
It all depends on your weight, ability to withstand hard impact (running is very hard on your ankles and knee joints), and ability to keep a steady pace (5.0mph-6.0mph is a very good clip).
For most people, a treadmill or running outside with a pedometer for 1 mile in the morning every other day, after you have woken up, works.
Don't eat until after an hour after you have worked out. If you can't do this in the morning, then wait 3.5-4 hours after you have eaten at night (although it's not as effective as running in the morning).
After you start dropping some weight, start a weight training program. Increased muscle mass will cause your body to draw even more calories for fuel, and it will boost your metabolism.
As far as dieting goes, it's ALL crap. Low-carb, high-fat, all of it. You cannot get around not exercising. For myself, I boosted the amount of veggies I eat to where it's over half of my diet. Pizza, chinese and mexican has to wait til Sunday when I'm not exercise.
Replace the soda you are drinking with water (soda makes you retain water like hell). If you can't stop glugging that Mountain Dew, force yourself to drink a bottle of water for every cola you down. Vending machines are evil.
There are also other things you can do to get the weight to come off and stay off... find things to do other than slave yourself to the computer! I took up skydiving (yes, I know, not for everyone). Find outdoorsy stuff to do.
Good luck
... but Unix/Java programmers aren't. Wanting to write the code for free, too?
Still running on an old 386SX NSF server with 125MB of HD and NE2000 card. :-)
Okay... so everytime a pay batch is run the server is going to do a bunch of GDI graphics drawing? I don't think so.
The fact that when you launch a Windows server a GUI comes up doesn't mean that the GUI is going to sit there and drain a huge amount of resources against whatever business process you having running on the server (unless the batch is doing some GDI work, such as stamping logos on paychecks or spraying barcodes or some silliness like that).
The argument of "well, you can run Linux with no GUI" is really lost on me. The Linux box is probably going to be running web services or servlets anyway... having an idle X session on the box is no different than having an idle explorer.exe process running on a Windows machine.
Politicians here have to spend lots to get the dead to vote... but they manage to turn out year after year. How failful to their citizenry after they're gone...
McBride, who is fluent in Japanese, will visit with several founding members... Translation? HI MY CODE MAKE YOW AIX GO SUCKY-SUCKY. I FILE IP SUIT, YOUR COMPANY GO **BOOM!***
Only two sections are complete.
When will I be able to get this in paperback so I can read it while I'm sittin' on the can?
Temporarily down, thanks to /. :-)
My my my, we need to cache these "cites" before we unleash the hounds.
From Microsoft's site:
L ie -- ????
The following new "shims" are added:
AddProcessParametersFlags
GetVolumeInformation
Let me see: Tapping a phone line is not an invasion of privacy but capturing the electromagnetic waves that pass through my body IS? This is not a technologically logical argument here.
Had the FBI broken into the home and tapped the machine, THAT would have been an invasion of privacy. Had the FBI planted a trojan horse on his computer, THAT would have been an invasion of privacy.
Face it, this technology has been out for years. The guy should have known and/or shielded his computer, pure and simple.
1. Click Start, Settings, Control Panel.
2. Click Add/Remove Programs
3. Select Outlook Express
4. Click Remove or Uninstall (depending on OS version).
5. Go get a copy of Pine compiled for Win32 and install it ASAUC (As soon as you can).
{awaiting the flame-bait}
This was first proposed after Voyager I and II flew past the planet and took high-resolution pictures of Europa's surface. Since then, it has been touted as a possibility from non-scientists like Issac Asimov all the way into movies (a.k.a. 2010 A Space Odyssey).
If there is any life to be found, it's probably some awful mold that any ordinary domestic scientist would promptly kill with Lysol.
-C
Most speakers at last week's NetMedia'2000 conference in London proclaimed WAP a temporary aberration that delivers substandard services.
British and continental newspapers are full of stories about WAP phones that don't work and services that are difficult to use.
Many commentators point out the simple fact that since you have a phone in your hand, most tasks are faster to perform by simply placing a voice telephone call than by using WAP.
Things have changed greatly: October 1999:
I was a rather lonely voice when I called WAP the Wrong Approach to Portability in my October 1999 Alertbox.
Most other commentators were very keen on WAP during 1999 when the hype was in full gear. April 2000: As recent as during my last trip to Europe in April 2000, most people had great expectations for WAP. Cooler heads who had conducted initial usability studies of the first WAP phones did raise a few concerns in April 2000, but the received wisdom was still in favor of WAP just a few months ago. May-June 2000: The picture started changing and the first negative reviews were published in European newspapers that had tried WAP services and pronounced them useless. July 2000: A new consensus has now been reached: nobody predicts great things for WAP any more. The excitement has shifted to:
Future mobile services with bigger screens and faster, always-on connections (except for the British telecom company Orange which cluelessly supports a technology called HSCSD with an unpleasant need to dial up every time anything is downloaded).
The Japanese I-mode system which is superior to WAP as a current-generation service.
Seems like WAP was already doomed last year. The Brits and euro web developers were already shunning WAP last year.
I can still remember the system architects at work drumming up white papers to convice an outpouring of cash into R&D for WAP but it never quite got anywhere. Who has the time to drive (late) to work and do their makeup and hair much less key 4445533111229955 on their cell for the favorite stock quote?
We don't need Internet cell phones. We need decent transfer rates through the PC/PDA to cell-phone adapters first!
-Tired of wasting minutes synching @ 9600baud.