This post originated from an RSS feed registered with .NET Buzz
by Sudhakar Sadasivuni.
Original Post: Visual Studio .NET : a TOY? or a Machine Gun ?
Feed Title: {Sudhakar's .NET Dump Yard;}
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/ssadasivuni/rss.aspx
Feed Description: using Sudhakar.Dotnet.Blog.Main;
I am still wondering how many of a typical developer pool write thier own unit test cases for .NET. This is due to the lack of architectural background in many developers and great abstraction in Microsoft's technologies. Upto my observations, the Java guys are far ahead of these things since they have a large scope of error prone factor. The higher degree of abstraction spoils the developer's ability to build software by making him as an end user of the technology. But still there is an oppertunity to break that abstraction in .net. But the technology and tools like VS.NET hides that creativity and capability by doing more than enough.
Though VS.NET gives more productivity by decreasing the work hours, It gives you a pipeline look, where you cannot think of other way also. e.g. In whidbey, you can get one DataGrid with Bi-directional sorting, Editable, Nice formatted features with out writing a single line of code. This kind of features will have a risky edge of making the new developers blind in coding. I have seen most of the developers putting blank feelings on faces for questions on internal things like this in my interviews.
On the otherhand Intelli JIdea and Eclispse are growing like VS.NET, but I could see many of good things, which are making developer to think. My only concern is why should we make any language as a kid's toy as well as a machine gun at other end? The reality is : Most of the developers are opting that "TOY" only.
I must admit that Microsoft's PAG is doing a very good job in pumping the architectural knowledge in to Microsoft developer communituies. But at the same time there is no development going for architectural extensions to Visual Studio.NET from microsoft. Most of the MSDN seminars in india are focusing on a common VB developer who knows; by double clicking a button, you can an event for that. I am 100% sure that .NET lacks that architectural touch atleast in the hands of a common developer.
Previous Topic
