TMobile really does have 3G in something like 240 cities... I know my city wasn't turned on until Late December. But many places have 3G now. And they are supposedly updating to 7.2Mb and then soon HSDPA+ (21Mb) which I think would then make their limited coverage the best. However, their rollout was amazingly slow and I was about ready to give up on them. And more than that, supposedly they have already turned on the 7.2 EVERYWHERE, but it definitely is not turned on here. So I see 5-700kb instead of 4-5000kb. Which is pretty pitiful. But the Android Nexus One is freakin' incredible -- I'm not having the 3G problem that has been reported elsewhere, its just slow here just like all the other 3G phones are that I tested.
Verizon was awful, Spring was Awful, AT&T was fine I guess, but I wasn't there long, I left because I couldn't get any coverage at work. T-mobile has been great (comparatively) as a company but their coverage has been meh so far. I'm still hoping its going to pull through this year and then they really would be the best.
The only thing I would like to add to this post is about meetings, iterations, and testing.
A lot can be said on this subject, I am going to try to make it brief and let you do the research.
Small iterations will help motivate, I suggest one week. Everyweek You get together to see how things have gone, and talk about what you will do for next time. Make them have input into what they will get done for next time.
Have a short daily meeting (about 15 minutes or less -- often called SCRUM meetings) to help identify what a person might be stuck on. If someone is stuck on a problem, identify it immediately, and get someone that can help (probably you) to work with them until it is solved. This removes risk as soon as it is found.
You cannot do enough testing! You need to be focussing on building automatic tests, that the entire project can go through. For instance I use Junit for unit testing each object in the system. I use ant as a build script and can test each piece as it is complete.
You implementation will vary, but "make" will work on all systems, and there is always a way to automate testing. Do it! Rebuild the code every day and what is broken can be fixed while it is fresh in the minds of those who broke it.
You must communicate more and get them more involved in what will be delivered (and shorten the iteration cycle).
Good Luck
Slashdot Mirror
Meh. It looks okay IMSFHO, but it is kinda childish. Liberation Mono is a much better fixed width font. Again only in my SFHO...
On the serious side, if you have used Liberation Mono you should give it a try.
TMobile really does have 3G in something like 240 cities... I know my city wasn't turned on until Late December. But many places have 3G now. And they are supposedly updating to 7.2Mb and then soon HSDPA+ (21Mb) which I think would then make their limited coverage the best. However, their rollout was amazingly slow and I was about ready to give up on them. And more than that, supposedly they have already turned on the 7.2 EVERYWHERE, but it definitely is not turned on here. So I see 5-700kb instead of 4-5000kb. Which is pretty pitiful. But the Android Nexus One is freakin' incredible -- I'm not having the 3G problem that has been reported elsewhere, its just slow here just like all the other 3G phones are that I tested.
Verizon was awful, Spring was Awful, AT&T was fine I guess, but I wasn't there long, I left because I couldn't get any coverage at work. T-mobile has been great (comparatively) as a company but their coverage has been meh so far. I'm still hoping its going to pull through this year and then they really would be the best.
The only thing I would like to add to this post is about meetings, iterations, and testing. A lot can be said on this subject, I am going to try to make it brief and let you do the research. Small iterations will help motivate, I suggest one week. Everyweek You get together to see how things have gone, and talk about what you will do for next time. Make them have input into what they will get done for next time. Have a short daily meeting (about 15 minutes or less -- often called SCRUM meetings) to help identify what a person might be stuck on. If someone is stuck on a problem, identify it immediately, and get someone that can help (probably you) to work with them until it is solved. This removes risk as soon as it is found. You cannot do enough testing! You need to be focussing on building automatic tests, that the entire project can go through. For instance I use Junit for unit testing each object in the system. I use ant as a build script and can test each piece as it is complete. You implementation will vary, but "make" will work on all systems, and there is always a way to automate testing. Do it! Rebuild the code every day and what is broken can be fixed while it is fresh in the minds of those who broke it. You must communicate more and get them more involved in what will be delivered (and shorten the iteration cycle). Good Luck