SI
SI
discoversearch

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.
Strategies & Market Trends : VOLTAIRE'S PORCH-MODERATED -- Ignore unavailable to you. Want to Upgrade?


To: Jill who wrote (5432)10/4/2000 9:35:02 AM
From: im a survivor  Read Replies (1) | Respond to of 65232
 
<<buy puts, a strategy I am not versed in at all.>>

I must admitt, I do not like buying puts for one reason. You are spending money...money going out of your account instead of in. I hate paying insurance, and that is essentially what buying a put is......Now, On the flipside and in gloomful hindisght<lol>, I'd give anything to be able to go back in time and buy some puts on mainly QCOM and CMGI, as we all know what has transpired since the beginning of the year.

Additionally, I would imagine buying puts should be done when the market is near overbought, not oversold. When your looking at your account as I did at the turn of the year, and you are at your highest point you've been, and the exuberance is high.......is the time to maybe buy some PUTS. Lets face it, most peoples downfall was the same as mine. They could have, and should have sold before all this carnage started, when all of our accounts were the highest they have ever been. Instead greed took over and we started calculating that with another double in this and double in that.....bla, bla, bla.....instead of being greedy, we should have been smart, protective and more levelheaded. If not sell, at least buy some puts. At very extreme overbought levels CC"s may give you a little premium, but they are no help in a stock going from 160 - 30 in a month or 2. PUTS would be the ticket for sure.

keith@prayingfor4000not3000.com