Here are a few good reads on the impact of the fiasco with some snippets below:
Investors.com
"Hardware purchases will be postponed, software upgrades will be postponed and customer projects will slow. This is not a time for (corporate customers) to take big risks. No big spending decisions will get made."
"Total revenue for the Indian outsourcing market is down 31% this year"
"Disruptions and uncertainty for U.S. financial markets are likely to delay some new software projects until the fourth quarter or next year"
ZDNet.com
"Right now, there are four clear survivors: Goldman Sachs, Morgan Stanley, Bank of America and J.P. Morgan. Tech spending elsewhere may go kaput. "
"Infrastructure consolidation projects will last for years. In IT spending surveys demand for consultants hired by the project remains strong. "
"Project managers will be in demand. Systems integration skills will be critical and you’ll need project managers to consolidate all of those applications and data centers as well as rearchitect systems. "
Ganesh Nagarajan of Zensar.
"The preliminary analysis of the current situation indicates that the impact will be short term and company-specific and though all strategy planners will continue to keep a watch on any further downstream impacts"
Computerweekly
"Tactical software and hardware spending will be hit first, followed by the more-strategic IT services in the long run"
"Software as a service could be a winner from this as could any model where people pay on consumption rather than up front cash"
Yeah, I am lazy!
Corporate IT Gotchas Indian Business
Linking and Sharing
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Impact of the financial services meltdown on the tech industry.
Trackback
Trackback URI for this entry:
http://www.prakashonsoftware.org/blog/index.php/2008/09/29/impact-of-the-financial-services-meltdown-on-the-tech-industry/trackback/
I have taken up aeromodelling as a hobby. People in the know told me to invest in a Super Cub trainer and I swallowed hard, convinced my partner that I am not regressing to my teens, and paid up the 160 bucks.
A few low altitude (never managed to take off!) but high spirited adventures left my plane broken, but thankfully not as broken as my ego. I sucked up, and signed up with an RC flying forum and made my first post got me free and unanimous advice that I needed to buck up and invest in a flight simulator. I doled out another 40 bucks and bought a simulator and installed it in my old Celeron, time machine…oops…machine. Well, I can bet, it does slow down time. Needless to say, the high end graphics turned my tortoise of a machine into a paraplegic snail. I tried all the tips and tricks that Google could dole out till I realized that I my C drive had only 400 MB free. I almost got suckered into buying Partition magic for 70 dollars till better sense prevailed and I downloaded Gparted.

It is free, fast and can do wonders for your machine's speed, especially if you are low on space on your C drive. No, the simulator is still not what it would be with a great graphics processor, but I no longer have the option of making tea between the time I click the IE icon and the time my home page comes up.
Gotchas
Linking and Sharing
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Great way to improve your desktop speed : Use Gparted
Trackback
Trackback URI for this entry:
http://www.prakashonsoftware.org/blog/index.php/2008/06/11/great-way-to-improve-your-desktop-speed-use-gparted/trackback/
CNN's list of career gotchas inspired me to come up with my own ones for software services.
Proposals should be done by offshore: Broadly speaking, there are two aspects to any proposal a). The sales pitch comprising the Story, how you want to position vis-a-vis the competition and the value proposition b). The technical approach, timelines ,costs and all the delivery yada yada (usually cut pasted from other proposals). There is nothing wrong in taking offshore contributions for a proposal. In fact all delivery related aspects must be owned and driven by offshore. But unless the guy who is close to the customer moderates and drives important differentiators are likely to get missed out.
The client is wrong: It is human to err. Or is it? In this business, the client is always right and yes, clients are human. There are times when clients make mistakes and the vendor ends up paying a price. Take these as learning opportunities, introspect, and see what you could have done to avoid the mistake. Maybe there was a communication gap that you could have resolved proactively but did not. Understand the client as a person and not just as a 'client'. Cover up for him when he has a slip up,make him look good in front of his boss and don't keep score. You might take a tactical blow once in a blue moon, but you'd end up building a solid long term relationship. I don't mean that one takes anything and everything lying down, but with customers it is important to pick your battles wisely. You cannot win a fight against the customer, you can only fight to win him over.
Saying 'No' to the customer: Never ever use the word 'no' in front of customer. Just go back to the time when you were a little boy and someone said "no' to you. How did you feel? Paralyzed? Rejected? Angry? Now imagine if your child were to say "No" in front of you. You would feel even worse than your child did when you said "no" to her. Outraged, confused, and wanting to punish your child for her impudence. After all, you are more powerful than your child. Now, clients have more power than you do because they sign your paycheck. It is easy to imagine what the word "No" does to the client's psyche. So, what does one do if the client makes unreasonable demands to which you simply cannot say "yes"? Well, reframe the demand as a requirement. If the client says, "I want this project for under $10M" and you are damn sure, it cannot be done for less than $12M, reframe and say "I understand what you are saying. You need a highly cost effective solution that stays within your budget" By reframing the unreasonable demand as a requirement, you are emphathizing with the customer and have turned the emotionally charged demand into a mutual goal that both of you can work towards reaching. Often, the client might be saying what he is saying just because he feels you are taking him for a ride, or because he needs to feel in command. The minute you give psychological air through genuine empathy and a real desire to help, accompanied by the willingness to be transparent, the defenses are down. There is simply no place in a salesman's dictionary for the word "no".
Quality assurance is not my job: While it maybe true that quality was considered more 'glamorous' a decade back than it is today, the fact remains that if you don't do a quality job with your execution, all the front end sales savvy and consulting magic is not going to work. Quality in execution is and will remain the bedrock of the industry. Quality needs first rate people and quality begins with each employee and ends with her. It cannot be shoved into a corner, into a group or a department. It is everybody's job including that of the salesman who sells.
If only I had more time: This is a tough industry. Work follows the sun and when you are asleep someone else on the other side of the globe is creating 'work' for you to do when you wake up.

Stop cribbing about how with a little more time, you could have done a much better job or had a more fulfilling life. It only makes a person look incompetent.
Gotchas Indian Business Outsourcing
Linking and Sharing
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Five worst things to say in a software services job
Trackback
Trackback URI for this entry:
http://www.prakashonsoftware.org/blog/index.php/2008/05/24/five-worst-things-to-say-in-a-software-services-job/trackback/
My wife pointed me to this interesting email forward. Kudos to whoever wrote it.
1) Project Manager is a person who thinks nine women can deliver a baby in one month.
2) Developer is a person who thinks it will take 18 months to deliver a baby.
3) Onsite Coordinator is one who thinks single woman can deliver nine babies in one month.
4) Client is the one who doesn't know why he wants a baby.
5) Marketing Manager is a person who thinks he can deliver a baby even if no man and woman are available.
6) Resource Optimization Team thinks they don't need a man or woman; They'll produce a child with zero resources.
7) Documentation Team thinks they don't care whether the child is delivered, they'll just document 9 months.
8) Quality Auditor is the person who is never happy with the process to produce a baby. And lastly…
9) Tester is a person who always tells his wife that this is not the right baby. Bullshit Gotchas Project Management
Linking and Sharing
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Funny side of software delivery.
Trackback
Trackback URI for this entry:
http://www.prakashonsoftware.org/blog/index.php/2007/09/21/funny-side-of-software-delivery/trackback/
My recent attempts to get back a tax refund lead me to the tax dept's website which had a prominent marquee running that said "New Income Tax blog". Here's the landing page of the blog. Yes. That's correct. You need a goddamn login id and a password to read the "blog" and there seems to be no way of knowing how to get login credentials. If someone can help me get into this blog I would love to know what the babus in the tax dept are thinking. Will be a good case study on how not to use blogging as a medium.
Bullshit Consumer Internet Gotchas Indian Business
Linking and Sharing
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Indian Income tax dept blog.
Trackback
Trackback URI for this entry:
http://www.prakashonsoftware.org/blog/index.php/2007/06/15/indian-income-tax-dept-blog/trackback/
You see it everywhere. Right from Microsoft's billion dollar products to simple .NET applications. Features that nobody wants to use, but everybody is made to pay for. The over-engineering malady stems from wrong assumptions, philosophies and attitudes.
More is always better: More is not always better. Packing in features that nobody wants increases the chances of bugs in the features that people really want, makes them pay more for these buggy features and slows down time to market. The marketing folks who are reading this would probably feel that without some over-engineering they cannot sell the product. Agreed! More could possibly be better for the company making the product, but almost always bad for the end customer.
We need to plan for the future: Let's face it. Most of the time you cannot predict future requirements. Requirements change and that is the fact. The way around that is not to predict and wire in your 'bets' into your requirements but to make the right decisions in the design. However, watch out for the flexibility mania in design (see below).
Product marketing over zealousness: Rand Eckfeld's IEEE paper brings out the importance of using Agile principles in strategic planning. "Projects must be coupled with a complimentary approach to strategy to in order to achieve the overall business goals. If agile development is to continue growing in the business community, complimentary strategic planning capabilities must be developed that share the same agile philosophies. " Product marketing would do well to apply Agile principles during customer interactions to stabilize and prioritize requirements better. Often product marketing has only a strategic feel of what the customer wants and distills this feel into a 'creative' product requirements specification setting off over-engineering. Steve Garnet explores the idea of Agile in business more fully.
Flexibility mania: Joshua at Dr.Dobbs defines code level over-engineering as "When you make your code more flexible or sophisticated than it needs to be, you over-engineer it."
Gotchas Products Project Management Strategy Technology
Linking and Sharing
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: The over engineering trap
Trackback
Trackback URI for this entry:
http://www.prakashonsoftware.org/blog/index.php/2007/06/10/the-over-engineering-trap/trackback/
I sometimes receive LinkedIn networking requests from like minded professionals which I welcome and reciprocate. But this one was different. I can't imagine people going to the extent of impersonating a corporate honcho in an attempt to get connections. I received the following regular email (not linkedIn request). Read on to discover contact baiting.
Hello,
I am an advanced networker on LinkedIn, and was hoping that you could send me an invitation to my linkedin account to join your network. My name is <Insert a Fortune 10 VP's name>, and my linkedin e-mail address is xxxx@public-email.com. I have a few thousand connections on LinkedIn - and I endeavour to add more qualified individuals to my network in order to expand everyone's access to other professionals and individuals who benefit from the social networking offered through sites like Linked In. Please see my personal networking contract below.
My profile on LinkedIn is located here: Insert a genuine link to the Fortune 10 VP's profile.
NAME’S PERSONAL NETWORKING CONTRACT
What does it mean to be a connection? I established my Personal Networking Contract to share my thoughts and expectations. It's my pledge of support for my network.
I would be honored to be a part of your personal network. That carries a responsibility that I take seriously. I pledge to help, support, and inform you so that we both may grow and succeed in our personal and business endeavors. The following outlines some specific aspects of my commitment.
I trust you feel similarly in return as a part of my network.
CURRENT. I will provide current information on my email address(es), other forms of contact as appropriate, and my availability either directly or through our mutual online network. I will make sure that my primary email address is current.
TIMELY. I will endeavor to process your online network requests on a timely basis. Sometimes this will be same day. Generally this will be 3 days or less. However in case of vacation, travel, or personal or business emergency, the delay may be up to 1-2 weeks.
CONTACTS. I will use the online network where we are connected for requests or contacts over that network. I will not ask you for email addresses of individuals unless you and I have a close relationship and there is an emergency.
UPDATES. Staying in touch with your contacts (or "pinging") is a fundamental part of networking. I will send you updates generally no more than once every six months. These updates may be of a personal, professional, or business nature. I invite you to similarly update me. If I contact you more frequently than an average of once a month, I will provide and use a separate opt-in process for such communications.
USE EMAIL. I will not use default forms for updates as they do not respect you and your time. They provide virtually no information and force you to start up your browser and then search for what is new on my profile. Instead I will provide the new information for the updates in the update email subject and body itself.
Thank you,
XXXX
Bullshit Gotchas Life
Linking and Sharing
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Exposed: LinkedIn Contact baiting scam
Trackback
Trackback URI for this entry:
http://www.prakashonsoftware.org/blog/index.php/2007/05/03/exposed-linkedin-contact-baiting-scam/trackback/

Anonymity is prized in today's world. True. Sites like Anonymizer have flourished for more than a decade thanks to the basic human right of wanting to reveal to the outside world only what the individual desires to expose. Fair enough. The problem arises when people attempt to misuse anonymity. JP highlights the dangers that anonymity can potentially cause. The recent Kathy Sierra episode could have been prevented had we had complete onymity without any ambiguity.
In my own view though, the critical need is to balance the risk of abuse of authority with the risk of abuse of anonymity. If people in authority themselves seek shelter under anonymity that is a sure case for complete onymity. *laugh* Anonymity is not so much of a danger so long as the power dynamics are skewed (anonymity seeks to balance the same), “collective intelligence” can be banked upon to override misuse of anonymity and misuse of power is a bigger threat than misuse of anonymity. Eg. An employee satisfaction survey could be completely anonymous.
Take an election. Before the election, the power is with the people and the real risk is one of misuse of anonymity by voters. Hence voters are onymous. Once the election is over, power of authority is with the politician. He can target individuals who have gone against him. Hence the votes themselves are anonymous. But some politicians are smart enough to target whole constituencies that have gone against them! Stephen Smoliar seems to agree with this line of argument with an amendment that systems can be fragile…..
"Prakash has hit an important nail on the head. I would like to amend it, however, with the observation that systems that deal with misuse of power, when they exist at all, are highly fragile."
PS: Hope Kathy starts blogging again. Her marketing insights are unique and I will miss them.
Kathy: If you are reading this. Don't let cowards who hide behind login id's bother you. The vast majority of the blogsphere is with you!
Gotchas Life
Linking and Sharing
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Anonymity versus Onymity
Trackback
Trackback URI for this entry:
http://www.prakashonsoftware.org/blog/index.php/2007/04/07/anonymity-versus-onymity/trackback/
Worldmapper.org is an interesting site that provides maps of the world based on different parameters. Here's the map from the number of female managers perspective.

India does not even figure in the map properly! It is interesting to note that the US and Europe are leaders here. It comes as no surprise that they constitute the "first world". Economic progress is crucially dependent on harnessing woman power and by neglecting women we are effectively at 50% of our potential. Unless our politicians do something besides lip service, India is in trouble. Judy Rosener seems to agree in her book America's Competitive Secret: Women Managers and sums up the difference between men and women with this line: "Women speak and hear a language of connection and intimacy, and men speak and hear a language of status and independence. Men communicate to obtain information, establish their status, and show independence. Women communicate to create relationships, encourage interaction and exchange feelings." The funny thing is that even in a "developed" country like Australia, women managers seem to be on a decline as this management blog indicates.
Career Gotchas Indian Business Life
Linking and Sharing
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Where are the women managers of India ?
Trackback
Trackback URI for this entry:
http://www.prakashonsoftware.org/blog/index.php/2007/04/01/where-are-the-women-managers-of-india/trackback/
Vinnie brings up an interesting point with regards to culture. I agree with him. Talking of culture in India, the work ethic is pathetic compared to the West. In India people do not value personal time as much and tend to utilize office time less productively leading to longer hours in the office. Ironically, the folks who put in longer hours are considered "better" workers. The culture effectively rewards slack! He also mentions poor customer service in spite of better telecommunication. All this adds up to culture being a key ingredient in providing a sustainable competitive advantage. Most other things can be bought of the shelf and mimicked. You can buy the latest CRM software and train your folks to use it, but unless the culture is fundamentally customer friendly you can kiss the benefits goodbye. Gautam writes extensively about culture. Here are his views.
Gotchas Indian Business Life
Linking and Sharing
If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Culture: The key to a sustainable competitive advantage ?
Trackback
Trackback URI for this entry:
http://www.prakashonsoftware.org/blog/index.php/2007/04/01/culture-the-key-to-a-sustainable-competitive-advantage/trackback/