These days the oxygen of India is so adulterated with politic that you can not refrain from inhaling it, even you use masks.
politics is everywhere, you want to search for any technical information you get ads of political parties on web pages, you read newspaper, every page is colored with politics, you switch TV channels, you get ads of parties there too. So in short, I want to say that you can not run away from politics even if you hate it most.
Now when the environment to so politics friendly, how can I escape from writing something on politics, however I have written on politics in past too, this time let's try to make it a little interesting.
As the title of this article says, election from the eyes of an IT serviceman, so if you do not belong to IT or do not understand IT people's emotions then stop reading.
And if you are an IT fellow, working in development team or quality testing team, or as a technical consultant and want to see the political scenario as an IT guy, then go ahead my friend, you must read this article.
Here is a scenario, if I consider India as client and Central government as a production server, then we see that in last 10 years, the code in production server got corrupted, and needs to be either upgraded or should be replaced with new code. Client (India) follows a 5 yearly release process, means the whole code can be replaced or upgraded only once in 5 years. Emergency releases may possible provided that the production is completely down.
so once a code is released, our various development teams(political Parties) start coding for next release. Our client(India) does not have 2 team system, where best code of 2 will go to production, but we have several development teams. Whoever's code is passed by end user(Voters), only that code will be delivered to production. However there were only 2 big development teams for many years, who are coding for India, but now several small teams have been grown. In recent few releases India has deployed code written by one big team along with some small teams, because some of the crucial modules developed and integrated by small teams, and they given integration option to only one big team.
Here we name the teams, the oldest development team is called as team C, the other big team is called Team B and several small teams collectively can be called team X. So right now our production server is (dis)functioning on a code written by C+X.(anyways, Ctr+X means cut from everywhere and paste it in swiss production).
The code is traditional and runs on legacy systems, with very limited flexibility. End Users are now frustrated with the performance of production system. End users used to have only option that they pass the code by Team B. All of sudden a new team arises, team A, who claimed that they can develop a code which is most suitable for production, which will remove all the bugs from production. Team A claimed that they born to kill bugs from production, they are willing to clean the system, so that users do not get useless pop ups and they can work on production system easily.
We have several quality servers ( state government) which got periodically refreshed with the data from production, but they do not function exactly same as production, but somehow near to production. The big difference is load, there are less users per quality server as compare to production server.
So when Team A claimed that they have a revolutionary code which could fix all problems of production, then end users decided to test their code in one of the quality system(Delhi), in fact it can be called as a pre-production server. The code written by team A was deployed in Delhi, with the help of legacy system as they were short of some important modules. The code was tested for 49 days, since it was claimed that it is a revolutionary code and can bring drastic changes, so load testing was performed along with UAT.
Several bugs were reported, many times code was hanged, the main module of the code was so unpredictable that anytime it would stop working and hang(sit on Dharna). End users of quality system were happy for some time as they could see a totally new interface to use, they started testing the system heavily.
Before implementing the code, development team A claimed that it is purest of pure code they have delivered, so they do not expect any bug. Testing teams have reported several bugs but dev team was reluctant to correct any of their bug. In fact their code could not survive the load which was generated, they excused that due to firewall we are not able to perform. They demanded to disable the firewall, they even claimed that the antivirus is not good, they wanted to implement their own antivirus. When dev team was forced to follow the CMM-5 process they became angry and they deimplemented their code by themselves from the quality.
Now the Delhi quality server is down, and waiting for a new deployment.
Even after failing in quality server, dev team A is preparing code for production, they want to deploy their code in production. They say that Team C has corrupted the production but Team B will also do the same. Team A's dev lead is everywhere criticizing team B's dev lead. In fact still they claim that only they can provide clean code, some end users are still hopeful, however chances are less that their code is going to be deployed.
Business people says that Team B has a code which may be deployed in production, no one from Team B claiming that their code has 0 bug, unlike Team A. Offcourse they have some bugs in their code, some hard to identify and some they can not remove as they are using few unlicensed SDKs.
Team B is claiming that their code will be so robust and powerful that it will improve the performance of production, and so the business of client will be improved, they are claiming that they will save the system from Trojan, spams, and viruses. In fact they have implemented their code in some quality systems successfully and their code is running fine, no major bugs reported. There is one thing that is still horrifying for Team B.In 2002 one of quality server where their code was running crashed due to some important database table corruption, however they have somehow recovered the tables, but lost data. The data which was belonged to a certain group of user could not be recovered. That part of users think that the code developed by Team B is not suitable for them, so they may deny the deployment of Team B's code. But Team B's star coder, who has developed a smooth code in a quality server Gujarat, has become the face of Team B. People are starting to believe that he can write a good code.
Now coming to team C, which is also known for masters of legacy systems, since they run their code on legacy systems only, never upgraded, but this time they don't have a proper code. They are still trying to woo the end user, if any of their module could be implemented. The current production server was running on their code, and it is so much corrupted that India had to suffer major financial loss. But they don't bother. Their main programmer is trying hard to learn new technologies to write a better code, but he is not able to grasp the things. Still hopes are alive.
Team X, they are comprising of several small scale development teams, are also in race of production.Team X alone may not deliver the production code, but they could play an important role. They could provide some modules, and it may be possible that Team B or C or A can not integrate their code without team X's connectors.
So, the announcement is due on 16th May, who's code is going to deployed in production, is it Team B, B+X, A, A+X or team C. However the contest seems to be C, X, A v/s B.
Wait and watch.
at the end I would appeal to all of you, please go and vote for any team, but at least vote, at last you are the end user, who is going to suffer if correct code is not selected and business will suffer if stable and strong code is not selected.
--JaiHind
Cartoon from Internet.
