Learning is an Art

Yeah you heard me right today Atlassian JIRA 4.0 was officially released after doing many beta’s and release candidate…I was expecting that it will take people with a storm with opensocial gadget JQL and many other improvements yes it did took people with storm but for some other reasons and the reason was its licensing policy you can find details of same here and my favourite one is there reason of changing the licensing that’s really cool and pretty lame at the same time for reasons of increasing the licensing cost or changing it all together.

I really doubt the fact that any hundred people company will really like to pay $4000 JIRA and the biggest one is the Enterprise license now costs you double that is $8000 and the cherry one the cake is licensing is now based on number of active named users that means that if you have 100 users and you are now 101 ; you need to run behind Atlassian to upgrade your licenses.

I want to write more on this but may be some other lets wait and watch for reactions from other people; I will be back on this topic with more detailed analysis of pros and cons of same this was just an initial outburst.

I was never a ardent fan of facebook I signed up just to see what its all about and I found it some what interesting so I started using it occasionally; but couple of days back I noticed something has terribly changed in facebook application; I was not able to relate if I had ever earlier used this application and on top of it you even don’t have an option to switch to older version which is pity.
I don’t know what has caused these people to change it but I am sure of one thing that I am not going to use it in future any more this is not the way you should force on people you want.

The Python interpreter contains few easter eggs which expresses sentiments of Python developer by and large I will listing them down if you know more kindly let me know

1. If you open a Python interpreter, and type

, it outputs the following:

The Zen of Python, by Tim Peters

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!

2. On python interpreter typing from __future__ import braces

it prints the output as follows Traceback (SyntaxError: not a chance (<interactive input>, line 1)

3. On python interpreter type import __hello__

this outputs Hello world…

Those were few easter eggs which were there in Python pre-3000 release

An antigravity module is added to Python 3.0. Importing the module opens a web browser to an xkcd comic that portrays Python having an antigravity module

Kindly let me know if you know any more easter eggs.

Ballmer Peak

I agree with Ballmer’s Peak; personal experience if you have proper quantity of alcohol and than do coding you are highly efficient but have no comments on whats that quantity as when I try I am not able to reach to that level but some time it happens on its own.

So alcohol is good for programmers; just kidding.