My Job Went to India: 52 Ways to Save Your Job

Product Description

You've already lost your job. You may still be drawing a paycheck, but the job you were hired to do no longer exists. Your company has changed, the technology has changed, the economy has changed, and the ways you can add value have changed. Have you adapted to these changes? Or are you at risk?

Architect your career
Economic downturn. Job cuts. Outsourcing. The ever-changing tech landscape. The threats abound. Chad Fowler is here to offer 52 ways to keep your job, despite the vagaries of the market.

* It's all about making the right choices. Choosing which technologies to focus on and which business domains to master have at least as much impact on your success as your technical knowledge--don't let those choices be accidental. Chad shows you all aspects of the decision-making process so you can ensure that you're investing your time and energy in the right areas.
* It's all about skills. You'll develop a structured plan for keeping your skills up-to-date so that you can compete with both the growing stable of developers in so-called low-cost countries as well as your higher-priced local peers. You'll learn how to shift your skillset up the value chain, from an offshore-ready commodity to one in high demand.
* It's all about marketing. As with any product or service, if nobody knows what you're selling, nobody will buy. Chad shows you how to create a plan for marketing yourself both inside your company and to the industry in general.

Like it or not, the IT career landscape has changed. This handbook will teach you what you need to do to avoid being left behind.

About the author Chad Fowler has been a software developer and manager for some of the world's largest corporations. He recently lived and worked in India, setting up and leading an offshore software development center for a large multinational company.

Product Details

* Amazon Sales Rank: #494608 in Books
* Published on: 2005-09-19
* Original language: English
* Number of items: 1
* Binding: Paperback
* 232 pages

Editorial Reviews

About the Author
Chad Fowler is co-director of Ruby Central, Inc., and remains an active, driving force in the Ruby community.
Customer Reviews

52 Ways to be the "Best of the Best"5
This book was a much needed wakeup call with respect to the realities of software engineering and the international market for those skills. We all understand that international competition is driving businesses to reduce costs by outsourcing software engineering projects, but few U.S. software engineers have a plan for countering the effects of this outsourcing. Chad Fowler's first hand experience managing outsourcing teams in India allows him to provide a unique cultural and professional perspective with the survival techniques needed by U.S. software engineers. From the content of this book, it is apparent that Chad Fowler is experienced, current and knowledgeable in the magical and demanding art of software engineering management. This book provides 52 bullets of behaviors/practices for evolving into the "best of the best" in order to insulate yourself from the impacts of outsourcing - and he justifies each of these with real world examples. This book is a great companion to the masterpiece book "Pragmatic Programmer" by Hunt and Thomas, which addresses the craft of software engineering with equally convincing justifications and examples.

Insightful, great career advice for a beginner5
I just graduated from college and started working as a developer for a software company. Life in college is very different from professional life. I felt a little lost and wasn't sure how to manage my time at work and outside of work. I wasn't sure about how the world works outside of college. This book gave me some good advice and guidance. It is also a fun read and contains some useful facts and moral lessons.

Highly relevant practical advice4
Wonderful, easy to read, and well written to boot.

I was impressed with how well he walked the line regarding outsourcing - neither demonizing/denigrating the offshore programmer nor doing a Chicken Little impression of the "sky is falling". This is by far one of the most balanced treatises on offshoring that I've read.

His assessment of the state of the industry, as well as the strengths/weaknesses of the offshore competition for an IT job is generally spot on.

E.g., he notes that an offshore "specialist" is simply someone who has never worked on anything else (say 5 years doing nothing but Java), and does not indicate how well that individual knows the subject matter; and that paradoxically offshoring actually ends up creating a lot more jobs onshore - esp. for a "higher bracket of developers". He also notes the inability of most offshore developers to say "no" - the dreaded "just one more day" syndrome. Then there's the small matter of time lost due to communication issues between geographically distributed teams. And, I've been asked to sit in as an "English-to-English" translator on numerous occasions.

In short, the phenomena he notes are all ones that I've observed in the past few years.

Not that I agree completely with his cultural understanding of India though. Its difficult to see a culture that's literally thousands of years old and get a grasp of its underlying complexity in 18 months spent working primarily with IT workers. The professionals he works with are a product of a complex culture and its difficult to generalize based on such a specialized sample.

For instance, in the chapter on Mentoring he states that in the West "Everything is competition". However, in his Introduction he talks about having to hire 25 people out of 30,000 applicants in India. Yes, you read that last number right. I'm not sure how he reconciles these two facts in his own mind - but let me assure you that there's nothing quite like competing academically/professionally in India. (I'm constantly dismayed by the focus in our public schools here, on fostering a "everybody's a winner" attitude in schools).

However, to his credit his missteps are rare.

Read as a workbook on how American developers should optimize their interactions with offshore teams, this book deserves 5 stars.

* * * * * * * * * * * *

This book's other objective - on keeping your toolset sharp and ready does not fare quite so well.

My biggest issue is that there is not much by way of new advice. And unless you're asleep at your career's wheel, you're already doing much of what he suggests. Don't get me wrong - its not bad advice per se - though I did not agree with all the recommendations.

For e.g., he derides people from calling themselves specialists because they don't understand how to make a JVM say uncle. But then he recommends that you don't specialize in a technology stack such as J2EE, because it is not platform neutral. Specifically vis a vis J2EE and .NET, he says "master one and get good at the other". Spoken like a true "manager".

If you sit and think about the variety of software that comprises the J2EE pantheon in all its glory - I'd argue that you would find it difficult to be a specialist in every one of its areas, never mind also being "good at" the Microsoft stack. Not if you want to go home at the end of the day and have a life, that is.

I think I am pretty passionate about my career - but it does not define me, and it would be a great loss to me, if it did.

There are a few gems in here - like the Mind Reader chapter which talks about picking up 'water cooler conversational cues' from your coworkers about potential improvements and then making them happen in your down time, to seem like a miracle worker.

For the most part, the ideas end up being pretty much recycled from the grand old classic that is the "Pragmatic Programmer" by Andrew Hunt and David Thomas. That book is a must read - even though it is a bit dated in places today. In other words, this book is largely a retelling of that earlier work in a newer context.

This part of the book rated 3 stars.

* * * * * * * * * * * *

The reason I highly recommend it, is that love it, hate it, or /dis/agree with it, you'll come away the richer for forming your own opinions. These are a practitioner's thoughts rather than a theoretical dissertation - and that is worth its weight in gold.