Readers React: Agile Development, Design with Mono for Android -- Visual Studio Magazine

Readers React: Agile Development, Design with Mono for Android

By Readers of Visual Studio Magazine
09/01/2012

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.

Hero
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.

Tom
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.

Robert
Canada

About the Author

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

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.