An Agile C# Windows Mobile Developer Learns iPhone Development
1. It does make sense, but it's not like anything I've ever done. There is a reasonably good separation of concerns going on, but I'm not deep enough into it to assess its strengths and weaknesses yet.
2. "Coding" by drawing lines in Interface Builder feels like "coding" by dragging-and-dropping controls in Visual Studio, but it's not. I can't say I approve of coding with the mouse, but it is nothing like the drag-and-drop nightmare that you get with an undisciplined WinForms developer. 3. Where, oh where, is ReSharper for Xcode?4. Unit testing is a relatively high-friction proposition. I believe in test-first design, but I'm still too new at this to have a feel for the way unit testing ought to work for an iPhone project. 5. Windows Mobile offers a great developer experience and a lousy user experience. On the iPhone it seems to be the other way around... at least so far...


