The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

Sometimes we have to repeat ourselves before we are heard. Then again there are times where we have to perform a certain action the same way several times before we can carry on with what we want to do.

Repetition is the keyword here and for humans that is something we generally try to avoid. Yet our digital friends love repetition. They never get tired and they never get bored of doing the same thing over and over again countless times.

So it’s little wonder then that all modern programming languages give us various ways in which we can perform a certain action as many times as we need.

In python we have the for statement which gives us the power to loop over large collections of data very quickly and efficiently.

The short answer is, yes and no. It depends upon who you are. The purpose of this entry is to help you determine, yes or no.

Full disclosure. This entry is created on a Mac mini. And doing so on Windows 8 (Release Preview). If you are a developer, in my humble opinion you need to test on all platforms you expect your app to run or you are not much of a developer.

To be successful you need to leave politics in geographical territory known as Washington DC. My definition of that is: 14 mi.² of real estate surrounded by reality.

Only in politics can we afford to take sides. Those of us in IT, especially developers need to do our best to be all things to all people. Certainly this is a technical impossibility. However in our game we can get some points for at least being serviceable if not outstanding.

The iconic software company that is based in King County Washington has been getting almost universally slammed from it's recent Los Angeles press announcement about its entry into the hardware business with the convertible laptop/tablet known as Surface.

Certainly I can see the point that it is now competing with its hardware vendors/partners. Intel has done a good job in the arena creating 'reference designs' without competing with its partners.

There is another viewpoint which seems to be ignored. The cold facts are Microsoft is a public company. This puts Microsoft in a legal position of doing the most it can to return value to its shareholders. Failure to do so means somebody is going to jail.

Microsoft has a vision, which at the end of the day is, a certain way to get enough people to see enough value to hand over their money, to fulfill their fiduciary duty.