a blog of Taras Filatov

The game we’ve been developing for two months is finally launched in Apple App Store.

Meet iCombat, a variation of old good Atari game, made for iPhone / iPod platform:

Visit the website of iCombat to find out more.

It’s getting into custom for me to sign at least one NDA each day.  Ah, paperwork..

My post regarding finding the right iPhone developer (from developer’s perspective) got noticed by Odesk and it seems to be interesting for people so I’m posting it here. You may digg it to make it more popular.

I didn’t post about it here in my personal blog - but will do now - “making iCombat” blog is a story of our client from New York who is making an iPhone tanks game with us and it would be interesting to read especially for those who are going to outsource their software development for first time.

wa haa, I have passed online management test at Odesk.com 99% better than all the previous ppl and have got the 1st place

P.S. in order to show off I have put the banner in the sidebar to the right

My opinion on when it is bad for the PM to do the coding himself:

1.    When it seems easier to do the work by yourself than to explain, create specs, mockups, use cases for the developers which seems to take more time.

2.    When poor estimation and hands-on rush before the deadline becomes a system.

When it is good for PM to do coding:

1.    While demonstrating the scalability and all the features of the product during the meeting with the client.

2.    When there are single unexpected cases of overestimated workload and it is necessary to go hands-on to deliver product functional, 100% tested and on time.

3.    While researching into new ways of doing things and new technologies.

4.    When teaching the engineering teams or helping them with some particulars tasks in order to build better team relationships, increase motivation and deliver better products on time.

Have you got something to add? Please feel free to comment.