you don't think that value comes across exactly that way?
that said indians have a major cultural problem. they're way too nice, and they're also way too enduring, and they find other ways to vent that. when i was in the US they were putting their shit on the indians, because they knew that since they really wanted to stay in the US they would endure all the shit, and not talk back. some of these people got dumped on their 6th year, because that's when the employer has to decide on whether they sponsor a green card or just get a new one.
odesk encourages crap, because the people that come there generally don't think hey i'll get an awesome guy on there who i can't find in my environment. they think hey my project is super easy anyway. i'll get a cheap dude to build exactly what i want.
don't get me wrong i know some really good developers, and employers on odesk(well truth be told it's just 1 of either). but they're there no doubt.
what disgusted me the most was that the guy i was working with (who used odesk to get cheap developers) was thinking that he was doing them a favor. he thought of himself of some kind of savior, because he was helping indians so much.
When I've dealt with teams in India (rather than Indian folk in western nations) I've had problems with this. It's not niceness, it's being non-confrontational. To excess. When you ask if they understand (so you could offer help or training on a technical question, for example) it's "yes, certainly". And then a week later you get the email saying no progress has been made because they don't understand something.
It's irritating.
Although, when the collapse finally comes, and you've just accused someone of lying about understanding and they finally come clean and it walks all the way back to a guy they paid in school to help with their CS classes, then you can start to make progress. I was not in the office but the stories I heard of people being scared of being fired because they didn't "know" something were rampant. NetApp really tried to amplify the message that saying you knew when you didn't was a more egregious affront than saying you didn't know.
>>getting around people unwilling to confront their managers
Almost every time I've tried to do this, I've been screwed. The only option after that even I have is to go work under a different manager. You really have to play nice, actually that's putting in mildly. You have to show super sycophancy towards your manager, if you want anything that looks like a raise, promotion or a foreign travel.
Often you are just screwed if you don't belong to your manager's state, or don't speak his mother tongue.
I've been pulled up and scolded inside meeting rooms even for mild and faint feedback, let alone direct confrontation. Some times in the line of 'You don't want me as your enemy'.
That's one big reason why Indian IT is such deep irrecoverable mess. Good people get nothing, have no scope for growth. If you are good its assumed you are going to sacrifice your life working for everybody. To get anything you have to be a super sycophant. Or belong to your manager's state or speak his/her mother tongue.
So the only option for good people here is:
1. Immigrate to a western country. Get treated like crap. If you are luck you might get citizenship in a decade or two. Else get ready to go through putting up with crap for years.
2. Work in smaller teams of your mindset and do a start up.
I can suggest another option though, start building a portfolio and have open source contribution that put you out of the cheap crowd.I am sure there are enough jobs at good hourly rates for people who can deliver quality. Even our hacker news "seeking freelancer" thread s offer pretty amazing set of opportunities.
Please don't. Because those of us who have good experiences do not find it particularly necessary to be vocal about it. There are good places and there are bad places i.e. you have a choice. Even if you start with a bad place, then don't think twice and quit the job the day it starts to suck. As for the culture, I worked for all sorts of managers and never experienced any cultural bias.
This is a typical South India problem. Not to say that North would be a fair game for south indians but it is still not that harsh from what I have seen.
People do try to get in a comfortable group based on common factors and Language in India is a great factor.
This is an endemic problem across India.
We need broader cultural changes. I don't think I will ever see them in my lifetime or even in the next few generations. And merely going to a different place where there is the same problem with same people is hardly going to address any issue.
Places like Bangalore, Pune, Hyderabad, Chennai etc or even private companies/MNC hardly solve(d) these issues. They just offered a bigger playground for such issues to come to play.
This is basically 'sarkari naukri', your old Indian government job all over again. Except that just with small time cosmetic changes.
Some companies here have quite the reputation for being Maharashtrian strongholds where only locals are valued and promoted. And these aren't your tiny software shops; I'm talking machine-so-huge-you're-just-a-tiny-cog type companies.
In short, you have to deal with offshore teams in a way that is different from the way you'd deal with someone in your office. You either have to manage them in a way that is effective for them - but probably feels foreign to you - or you need to go back to local teams (or at least teams from cultures closer to your own).
Essentially, if you were a pilot, and your indian dev-lead was your co-pilot, you'd both probably crash a plane because he would be too polite to tell you that you forgot to put the wheels down. His way of saying this would be something like 'we found that more research into the wheels problem might be a useful idea', rather than 'hey captain, you idiot, the wheels aren't down!'.
[1] http://en.wikipedia.org/wiki/Hofstede's_cultural_dimensions_...
You're most likely spot on about the cultural reasons for the behaviour, I just wanted to point out that it doesn't come across to me as nice. It comes across as passive and obstructive.
And I'm English, we're pretty good at passive...
Actually, I just want to point out if you've had any training on how to run a training session, you ought to know that asking "do you understand?" is pointless in every culture. From an asian culture it can even come across as threatening and dominating. Its like asking "do you want to keep your job?". Who is going to stand up and say "actually, no I don't" to that? Work in a western company is often the very first time in peoples lives where voluntarily admitting you don't know something doesn't carry significant penalties.
I've never phrased it as confrontationally as you're assuming, it's always been a genuine offer of help.
Never has been pointless when dealing with European, American or Australian resident engineers (regardless of racial or cultural background), it's simply opening the floor to new questions. So now's who's guilty of sweeping assumptions?
Regardless, the original point still stands - this is not niceness, it's cultural conditioning to be non-confrontational to the point of dishonesty, and it's highly counterproductive.
I guess my point is that unless you're well versed in the culture, it's easy to trip over these things.
I have no doubt it's a cultural misunderstanding rather than an attempt at deceit, but then... how the hell do you communicate technical knowledge to people who won't tell you what it is they need to know from you?
Well, I have been in that same boat. My answer? Don't hire them in the first place, and try and avoid projects if that decision is made for you.
30 hours is not long to have to stick with one thing, and if you put in 30 hours on odesk at $10/hour you could take the next twelve and a half weeks off compared to what you are signing up for. Even at $2/hour you would still only need to work every second week and still come out ahead.
I can only guess that competition is fierce but you only need to find and retain a few companies that can feed you some work and you are set. So, sure do what you are planning if it keeps food on your table, but set each Sunday to match your month's wage and when you do, get out.
Next weekend when I'm working rather than spending the whole time with my family I'll rethink whether I could outsource it for 10% of what I make if I could find one programmer I could rely on to get it done correctly, quickly and discretely.
That's my first world problem.
I've found focus gets better with age. Young minds benefit the most trying to discover and learn as much as possible. You get bored when the initial learning portion vanishes.
Sometimes you need a project that has a wide enough breadth that it can hold your attention over a very long period of time. When one part gets boring, you move to the next part. Over a few months you rotate around but you must return to each piece and make it better.
I am trying to get a freelance webdesign/developer career going, but I am quickly learning that doing freelance projects is much more about getting clients, managing clients, and making sure they are happy than it is about programming, design or development skills.
Anyways, I hope you new job goes well and good luck!
I have this - and mine is utter crap. I cannot believe I have so little good stuff to show, despite years of doing this. (http://www.mikadosoftware.com/paul_brian). I realised that I also do not finish projects - but I have to finish something so I at least put it on github and link to it.
You can do better.
This surely must become a trend - looking on ODesk for a fool to do crap work must give way to CVs that demonstrate actual ability.
Running your own shop is a whole new set of skills. Working at this place might give you the insight for later in your life when you can move up the ladder. Maybe you are doing the right thing. Just get your focus fixed on the next level up and how you can get there.
edit: no, don't take this job. from your skill set I think you have already well passed this level. there's nothing to learn and it might even look negative on your resume.
Can you move down to Delhi ?
do you know if there are many northerners that move to bangalore ? plenty of AP and TN move there I know.
My late uncle used to say this over and over again: zamindar nahi banenge jab app kam kisi aur keliye karehe. If that didn't make sense, it's because my Hindi sucks: what I mean is you'll never get rich working for someone else.
There are programming skills that are valuable in
isolation. If you are a world expert on a certain domain
which lacks talent, then that's valuable.
Like Delphi? [1][1]
Get a down payment on that first gig and you have operating funds in a country where apparently there are developers working for $100 / month. You don't need to get an office right away. Work solo at first if you need to or pickup another local developer who can work from home. Or pick someone else up off O-desk. Build more funds and you get more options.
> And if you agree that (s)he can't do projects alone, why do you suggest making and monetizing her/his own projects?
Good point. We all have problems at times with discipline when working from home. It's something we can get over, but it also depends on the underlying reasons for the lack of discipline. You have more room to experiment when you are working on your own projects.
There are, at least when they're starting out. There are also those who work for $2,000 / month. Those are pretty much the two ends of the payscale for a junior dev.
SF has some of the best salaries for developers. Contrast that to India, where a "good" salary for a full stacker is about $15k per annum(!). Shit's ridiculous.
Wow! Now that's very good for a junior, isn't it.
I suppose it just says something about how diverse a country India is. It still baffles me a bit though.
No you can't, obviously. You just said it. For one, you don't enjoy it.
What you need to learn is that straight programming isn't a valuable skill by itself. You already know this because you wrote an article about it. You need to be able to tie your programming skills with other skills such as selling yourself as the person to get the job done. Once you get the job, you need to be able to ship it.
There are programming skills that are valuable in isolation. If you are a world expert on a certain domain which lacks talent, then that's valuable. But that's not really isolation, that's tying your programming skills with a certain specialty.
Take a look at the model you are working under. There is a whole spectrum of jobs from good to crap. On Odesk, there are a sprinkling of good and a lot of crap. I imagine the company employing you is saying yes to every job that comes their way. They probably don't get good jobs, so it's all crap. They get crap jobs which pay crap and of course you are going to get a small slice of a crap pie.
Why take a job just because it's there? Okay, you laid out a bunch of reasons but you still hate it. I would probably hate working on crap jobs also. People worked for Steve Jobs because the guy was... well... Steve Jobs. Why are you working for people who are trying to compete on the worst model in web development, the race to the bottom in pricing?
If you know good developers, then maybe you could start your own development shop and get those developers to work for you. If you hate the work but you can get jobs, then maybe do the selling and have the other developers do the work.
Or maybe you could come up with your own projects and monetize them.
You just have to hustle, just like everyone else does. You can't just write code and expect the world to come to you. Get out there and make things happen.
Edit: In other words, quit whining. ;)
Edit: Edit: I could write a book on this subject. The above is just an attempt at an off the cuff capture. There are a ton of threads on HN which are hugely valuable on bringing the bacon as a developer. Just look around, it's more productive than ranting about your situation.
Clearly the person you are working for is trying to take a "this is how everything is done here" approach to running a dev shop and hiring developers. It's the same in the Philippines. Everyone works 10 hour days, 6 days a week and within a certain band of salary. I suppose the U.S. is like that to some degree. We have the 9 to 5 and 40 hour weeks.
Disruption in your case would be pretty easy. If the company has decent employees, then you could scoop them all up.