DevExpress Newsletter 24: Message from the CTO

ctodx
24 March 2010

Now that we’re doing my Message from the CTO in the DevExpress newsletter as a video, I’ve had a couple of requests to make sure that I publish the text as a blog post. Here’s the Message from Newsletter 24 (the video is here):

Opportunity Costs

Last time I talked about sunk costs and the requirement to ignore them when making decisions between two different strategies.

This time, I want to talk about opportunity costs. In one sense it's fairly simple: if you have a decision to make about two mutally distinct outcomes, the opportunity cost of selecting the best choice is the next-best choice.

Suppose you have the choice of spending $15 on going to the movies or buying a DVD. If you select to go to the movies, your opportunity cost is the DVD. If you buy the DVD, the opportunity cost is the trip to the movies. In software development, opportunity costs come up all the time: we often have to make a decision about which project to take on, given a choice, and the opportunity cost of choosing a particular one is the best idea we didn't choose. Note that opportunity costs are not necessarily monetary, but can be related to anything else of value to the person deciding.

Closely related to opportunity cost is the notion of "There ain't no such thing as a free lunch", or TANSTAAFL ("tan stah full") as I tried to pronounce it when I first came across it. The free lunch term came about in the days when saloons in the States used to offer a free lunch to patrons who ordered a drink. In reality, the lunch wasn't "free" (that's free as in beer to quote Richard Stallman) but was paid for because the drinks were priced higher and patrons would usually have two or more drinks. In other words, tan stah full says: to get something we desire generally means giving up the opportunity to get something else. It "costs" us in some sense to make the choice; it is not free. This is opportunity cost.

At Developer Express we use the term sometimes to explain why we don't add a particular feature or control. We recognize that a given idea is valuable, but, since we have limited resources, we can only do it by not doing something else. The opportunity cost of doing a possible new feature over here is not doing another feature over there, and that second feature may in fact be more valuable in terms of revenue. However if enough people vote for or pester us about the first feature, it may be more valuable in terms of goodwill, for example. Opportunity costs may not be monetary, remember.

So, when thinking about what course of action to take, you should not only discount your sunk costs, but also consider your opportunity costs. Harder to evaluate perhaps, but definitely worth thinking about.

Free DevExpress Products - Get Your Copy Today

The following free DevExpress product offers remain available. Should you have any questions about the free offers below, please submit a ticket via the DevExpress Support Center at your convenience. We'll be happy to follow-up.
No Comments

Please login or register to post comments.