Showing posts with label coding. Show all posts
Showing posts with label coding. Show all posts

Sep 26, 2012

Price of the coding - is it a nationality issue?

Couple of weeks ago Finnish magazine 3T got their hands on secret internal report from an large Finnish company about efficiency of coders in different countries. Report stated that even though Indian coders cost approximately 30% of what Finnish coders do, Finnish ones are 4,5 times more efficient than their Indian counterparts. This then means that Indian coders turn to be 35% more costly than Finns eventually. (Source: (in Finnish) 3T - Salainen selvitys: Intialainen koodaus on suomalaista kalliimpaa).

I've worked with at least, Finnish, Indian, Chinese, Russian, Polish, Turkish, Slovakian, British, French, Mexican, US and Canadian coders and I have to say nationality doesn't make a difference. Despite the nationality there are really efficient coders and coders who just can't make it happen. There are noticeable national differences on work methods, but those don't explain the efficiency.

Trend in buying coding from some specific country drives to the situation, that there are too much demand for the knowledgeable resources. In these countries some less capable people do get hired and easily sold to high demand customers in countries where coding prices are high. This might make it look like coders in some countries are less capable than in others.

In countries where price of coding is higher, only the efficient ones get to keep their jobs. When the competition is fierce, less capable ones turn to do something else than coding (I bet many of you think managing of the coding now).

I like to believe that, in most of the cases price of the coder is irrelevant. Good coder can easily be 100 times more efficient than some other. I don't mean they make code 100 faster than others, but they can make much more clear code and create much less errors than others. So the overall result might be 100 times less work was done for some piece of software.

Also a good team can make a difference. Team with good internal ways of working, like code conventions, code review practices, architectural guidelines and open discussions will improve efficiency dramatically. These in their own sense make evaluation of SW project length a challenge. It's the team and following their efficiency that make it possible to estimate what's the cost and time of certain SW project.

There are noticeable differences in efficiency of certain coders and team of coders. I don't believe it's a nationality issue, it's always about how competent the individual and the team is. It doesn't make buying of SW development easy. What it should state to the buyers though, is that price is small function in SW development efficiency. There always need to be other measurements in use, to know the real price of the coder and the team.

Written by +Henri Hämäläinen

Feb 15, 2011

Considering options for the future

I guess you all already know that it's going to be hard time for all nokians in Finland. There most probably will soon be announced major layoffs and I'm under thread as almost everyone else. 

I've been thinking my options for some time now and one of the options would be running my own thing or co-running with some other guys. That's a long term dream and wish, but it's always so easy to find reasons why it's not suitable. Think of the following for example.

I would like to run my own business..
  • but I haven't made any code for some time and hiring external coders makes starting new business bit harder
  • but I have 2 small kids and girlfriend at home and I'm the only income for the family now
  • but we have big mortgage I need to be paying off
Even though these are real, these are still excuses. Couple a days ago I decided to again think on the way Dan Pink's book told me, "change the word but to the word and", meaning that realize the obstacles you have and think again what you could do to overcome those .

So I decided to start one by one checking if those obstacles could be overtaken. That would give me more options on what to do in coming year or so. So I started to learn to code again. I'll use at least one hour each day to code and see if I'm still capable. I'm not expecting to be a world class coder until summer, but at least it will be easier to think what creating SW from my ideas would actually mean. I have to admit that I've really liked it so far. I did start easy, just to motivate myself.

I've learned that worrying won't bring any solutions. Being positive, doing, failing and learning will. So I'm going to be positively looking whatever challenges there will be ahead in coming year or so. 

Quite a self motivating speech. If you got this far, you might have been the only one. I just had to write this for myself.

Written by +Henri Hämäläinen