Letters from Readers

Readers React: Agile Development, Design with Mono for Android

In a recent blog post, "Is Agile Really a 'Developer Rebellion Against Unwanted Tasks'?", Data Driver blogger David Ramel wrote about the mixed reaction from developers to his article about a controversial report on Agile software development from analyst firm Voke Inc. "Many people still seem unclear as to what Agile actually is," he observed. Several readers agreed, and some didn't. Here's a sampling of their responses.

I'm in my second position that claimed to be using "Agile." My experience has been that Agile is an excuse to not think things through and not document requirements. My current boss says things like, "My ideas are lumps of clay ... they're not fully formed." Yeah, thanks a lot, Agile, for making me do all the design and run around getting feedback from all the stakeholders on how something should actually function. I'm not saying you need to define things down to the smallest detail, but a little up-front thought and architecture goes a long way toward making better code and better products in the long run.

Posted Online

I'm really surprised by the report and lack of consensus among the developer crowd. To me it's bad news -- the level of general ignorance goes up, and people simply don't read anything anymore. I'll insist that reading a Wikipedia definition is enough to understand on a basic level the difference between an Agile and a non-Agile way of developing software. Agile is the result of decades of software development experience by a myriad of programmers. Many of its premises are not new and are proven by hard facts. So the real problems, I think, are ignorance, inability to change and fear of failure.

Yuri Sokolovski
Posted Online

New Designer for Android
Mono for Android columnist Wallace McClure took the new Xamarin Designer for Android for a spin and offered some tips in his online column, "Xamarin Designer for Android". Readers welcomed the addition of a design surface.

Yes, yes and yes! I find I'm constantly frustrated by overly feature-rich toolsets that don't explain a damn thing. Then they wonder why adoption is so low, especially by new coders. A designer does a great service in bridging the gap between toolset and coder knowledge. Why all tools don't include it, I will never understand.

Posted Online

Great article -- I think this really helps reduce the barrier to entry over porting .NET code to the Mono/Android platform. Thanks for this -- I didn't know it existed.


About the Author

This story was written or compiled based on feedback from the readers of Visual Studio Magazine.

comments powered by Disqus


Subscribe on YouTube