Skip to main content

Shorting Apple Stock

At the height of all the iPhone hooplah, I decided to short Apple stock.

Shorting a stock means selling it without owning it, and then buying it later to close out the position. The effect is that you make money as the stock goes down (instead of the usual way of making money as the stock goes up).

I sold Apple stock short January 10th. I then placed a limit order to close out the position (i.e. buy the stock to "cover" the short) at 10% below the price at which I sold it.

This morning, I received notification from TD Ameritrade that the limit order had gone through, so I made a quick 10% on my money.

Apple is a great company with great products (though I am skeptical about how some of the iPhone marketing will play out). Their success speaks for itself. However, smart investing (and trading) is not always a reflection on the company. No matter how valuable a company is, it is always possible for the stock market valuation to be higher than the fundamentals dictate. When hype and headlines run rampant, it's often a strong indication that prices have gotten out of line with fundamentals.

Every year, Apple holds its MacWorld Expo, and, almost like clockwork, the stock price goes through the roof as Steve Jobs announces new products. Over the succeeding few days, weeks, or months, the price usually declines significantly. There was so much hype about the iPhone this year that I couldn't resist cashing in on the pattern.

Comments

Corinne said…
Well I haven't gotten into calls and puts yet in the stock market, but I also followed the hooplah and made a quick buck on AAPL. Cheers to us! :)

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio