Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : TAVA Technologies (TAVA-NASDAQ) -- Ignore unavailable to you. Want to Upgrade?

To: Bill Wexler who wrote (19117)	6/24/1998 7:09:00 PM
From: Y2k_fan	Read Replies (2) \| Respond to of 31646

I was leaving a little respect for you. I will ask again, if you are so sure about TAVA, let's make this the last post on TAVA between us till the bet is over. You have three choices, Tomorrow at the open, 1) Short 10k TAVAs , 2) Sell 1000 Nov 7 1/2 naked calls, 3) Buy 1000 Nov 7 1/2 puts Do not close, hedge or cover your positions until November option expires. (If you want to chicken out, let us know, I don't want you to go broke.) We go back this board five months from now, neither of us post to each other till Nov option expires. You win the bragging right if you win, otherwise leave this thread alone. Stop your psychologic game here if you think that your so-called truth will eventually win. You can chicken out now if you admit that you don't know everything in the stock market. (which I already did.)

To: Bill Wexler who wrote (19117)	6/25/1998 7:17:00 AM
From: Paul van Wijk	Read Replies (3) \| Respond to of 31646

Bill, As a project-manager in the IT-business I'm used to do a risk- analysis before starting (or bidding on) a project. Let's do a little risk-analysis on the Y2k-project, Budget; 300 to 600 billion -> max. score Members of project-team; at least tens of thousands -> max. score Fixed date; yes -> max. score Number of program-languages; a lot -> max. score Different kind of hardware; a lot -> max. score Number of locations the project-team is working-> worldwide-> max. score Standards; yes, but unluckely a lot of different standards-> max. score Support of top-management; ask Al "superhighway" Gore; max. score Number of end-users; a few billion -> max. score etc. etc. So we are dealing with a project that has a maximum-risk score on (almost) every aspect of the project. So the next question is; what can we do to reduce the risk to an acceptable level; 1.Stop the project. If possible every manager would take this decision without any doubt. But it is not an oppurtunity on this project. 2. Change the end-date of the project; second most logical step, but also not possible on this project. 3. Drop functionality; one of the very few possibilities to reduce the risk, but we have to keep in mind that worldwide a few billion people are already working with the system. They probably don't like it when the new version of the system has (much) less functionality. And end-users will go bananas when reducing functionality will mean no functionality at all. Because for a long time the question (imo) is not IF there will be end-users with blank screens, the question is how many and for how long. And what will be the impact of it. Bill, I think you need a few reality-pills. On the other hand, we all make mistakes. Have a nice day, Paul