This entry doesn't really relate to software development, but nonetheless it covers human behaviour and subconscious decision making that does significantly impact our marketplace.
Here in Canada, a year or so ago there was a big kerfuffle in the federal government concerning transfats - a controversy that got a tonne of press (both by boosters encouraging this consumer protection, and critics who decried it as the actions of a nanny state). Namely, that there were calls to ban transfats from the food system, legally eliminating this purportedly dangerous, artificial fat from grocery shelves. This would have made us the second country, after Denmark, to ban transfats. Transfats are, of course, the hydrogentation of otherwise normal, in-moderation-healthy unsaturated fats, molecularly altered to improve handling (hydrogenated oils are solid at room temperature, and in fryers need to be changed less frequently), and reduced spoilage and possibly consumer convenience - goods stay "fresh" on grocery shelves for longer, while baked goods made with transfats, for instance, often stayed bizarrely fresh out of the package for days. Humorously, a couple of decades ago transfats were seen as the saviour from the evils of saturated fats.
While McDonalds, along with the other big fast-food companies, are addicted to transfats, and they're finding it difficult to cut their use of the stuff, I've been noticing more and more formulation changes on store shelves - I've always been a label reader - with transfats being voluntarily eliminated from whole categories. Occasionally this change has occurred silently (there was a mass migration from trans-fats in potato chip products about a year ago, with only a few of the companies actually noting the dramatic health benefit change), while in other case it has come with a huge marketing campaign. Even for those people blissfully unaware, the quantity of transfats in their diet has plummeted, apart from a couple of hold-outs like McDonald's french fries.
So why has this mass change occurred? I suspect two reasons:
Interesting seeing the impact public information, and the future threat of lawsuits, has had upon such a huge part of our marketplace. And in such a short period of time! Government intervention was entirely unnecessary (and might actually have slowed the switch, as what should be a simple health debate would inevitably turn into a bunch of partisan nonsense, with the opposition party and boosters sucking back a tub of hydrogenated oils in the name of freedoms, proclaiming the rights of all Canadians to eat transfats. Such political nonsense is typical in those scenarios, regardless of who is in power and who is across the floor).
Brad
excited by what he saw at PDC.
Brad
Feld, venture capitalist:
2006 Will Be The Year of
Microsoft.
[Scobleizer: Microsoft Geek
Blogger]
A surefire way of getting linked on Robert Scoble's highly rated
and ranked blog is to say
something promising about Microsoft, or to say something negative
about Microsoft in a way that Mr. Scoble can easily defuse while
pretending to agree with you (such as http://radio.weblogs.com/0001011/2005/09/16.html#a11174,
where Scoble subtly claims that Balmer was being misinterpreted).
In this case, a VC was drunk on the PDC, and like many before him
presumed that everything Microsoft spins is gold. Many foolish
predictions have come out of such a situation.
In any case, while Microsoft will continue to do very well by any definition, it's quite a stretch to call 2006 the year of Microsoft.
Undoubtedly Microsoft has some great products, but we're talking
about a company that needs to maintain a revenue of $10 billion a
quarter, and with programs like software assurance and the MSDN
program, these upgrades are long overdue. If anything,
these releases are about avoiding a loss of revenue stream rather
than an increase of revenue stream.
This technology demo is a fantastic watch, and is truly a revolution in the way data access will occur in our .NET applications. A LINQ technology preview can be downloaded for the just-released Visual Studio 2005 Release Candidate here. The LINQ project page can be found here. I'm trying out the LINQ technology preview and will post more thoughts shortly.
Another part of the LINQ project to watch closely will be the
Object Relational technology in
DLINQ. Both of these will be hugely useful in dissolving the
tremendous disconnect that has traditionally existed between
relational persistent storage and our code.
Tough to listen to the hype machine kicking up for C# 3.0,
though, given that C# 2.0 isn't even to production yet. It's great
to be prepared for new technologies, and to get your input in at
this stage so they can make it the best that it can be, but still
it's really difficult to find the time to learn currently
impractical technologies when there are so many practical technologies we can
learn to help us today.