In my humble opinion Microsoft made a slight mistake with the way they implemented ASP.NET in 2005. They should have split their documentation into at least three areas and defined a path through them that over time introduced newer and lower-level concepts as projects become more complex – and that this path should be kept independent from the whole certification framework and made generally available for everyone.

These three general areas should have been split into something like as follows:

1. Small sites that require only the highest level knowledge of ASP.NET – essentially this would be what come’s out of the box as most people new to ASP.NET understand it.
    
2. Medium complexity/size sites that require some control customisation and a greater understanding of the underlying technology. You could say that this is the point you start to wonder if ‘.ascx’ is going to do everything you want and maybe you might be considering a Web Service or two. You also may start to wonder if the 2005 version of web projects is cutting the mustard. You also find that class libraries are starting to look attractive.
    
3. Larger sites that maybe could be called ‘Enterprise’ or ‘distributed’ solutions. Here you would require a varying knowledge of the platforms and technologies from intermediate to exceptional. You instantly discover that the nice fuzzy world of ASP.NET isn’t that fuzzy after all and in fact can become a hindrance. You have to work more and more outside of the nice cosy ASP.NET world and ASP.NET simply becomes a thin layer façade over the real work underneath. You may also start praising Microsoft for caving in to the real world and releasing proper Web Application projects as part of VS2k5SP1.

It is not that any of the above isn’t possible to construct with everything that Microsoft makes available, merely that there does not seem to be an easy path through the possibilities for people and many developers new to the ASP.NET platform, while finding the initial transition easier than with the previous versions of .NET, find that there can be a very steep learning curve involved if anything more complex than the ASP.NET based controls is required.

One of the largest issues I encounter is related specifically to this learning curve, especially with individuals migrating from ASP, PHP or Coldfusion (although admittedly this is becoming less of an issue with PHP as many PHP developers are happily embracing the OOP paradigm as the language grows). Even though Microsoft’s marketing is proving successful with ASP.NET’s take up being faster that at any other time, Microsoft is making technical transitions potentially difficult DUE to with their marketing and high level fluffy features available in ASP.NET.

That’s the thing though, it *is* easy to create basic dynamic web sites with ASP.NET using many of the advanced drag-and-drop features of the IDE, so initially ASP.NET comes over in the most part as a breath of fresh air and in fact, Microsoft has excelled here. However, if you do need to create something a little more complex than the statistical majority represented by the smaller-site implementations, you have to start to scratch and look beneath that shiny veneer; this where many find that under the shiny exterior ASP.NET can actually be a complicated beast.

ASP.NET reeks of one aspect of the KISS (Keep It Simple Stupid) principle. In order to make ASP.NET easy to use for the masses they have had to stretch and contort everything. Most of it is exceptionally clever and ASP.NET is a wonderfully powerful reflection and JIT compiler engine. It’s because of this end-user KISS based design that Microsoft have inadvertently made the ASP.NET internals a bit complicated. Also because of this ‘ease of use’ angle Microsoft has completely ignored in many instances (except for the Singleton for example) the entire OOP design paradigm from MSDN and more specifically ASP.NET.

This is a huge travesty that is giving me the most cause for concern at the present moment.

Many well intentioned and possibly very skilled Web Developers are missing the point to .NET because of this. .NET is Object Oriented! Why the hell is Microsoft not telling people how to leverage this paradigm? Why are so many developers being left out in the cold in this manner with .NET?

It is because of this issue that I and no doubt many, many other developers/architects ‘in the know’ are finding that they are being employed to work on projects or teams that are suffering badly directly or indirectly because of a lack of knowledge in OOP, .NET and how computers really tick.

Because I don’t have time to do something about the situation described above, all I can do is give some general pointers…

So those four steps to ‘.NET Web Development’ enlightenment are in my opinion as follows:

1. OOP
   • Learn the basic pillars of OOP, ‘Encapsulation’, ‘Inheritance’ and ‘Polymorphism’ using the .NET language of your choice.
   • Learn how to use the Gang of Four design OOP patterns with the .NET language of your choice
   • Learn to think in these patterns so that when you are presented with a problem, you can state to other developers and business analysts the names of these patterns and why you think they are useful.
      
2. ASP.NET
   • Don’t use ASP.NET’s inbuilt tools simply for the sake of using them, they are sometimes too generalised and trying to be too many things for too many reasons.
   • Never use the newer Website projects in VS2k5 – Install SP1 and use real Web Application projects. Convert them if needed. Get away from the VS2k5 website!
   • Keep UI logic and Business logic separate. Don’t be afraid to use class library projects.
   • Use Web Control library projects instead of ASCX’s if appropriate, especially if the controls are to be re-useable for other projects.
      
3. Learn how your computer works; learn how .NET makes your computer work.
   • If you don’t know:
     • Why a string comparison is slower than an integer comparison
     • That ASP.NET isn’t just a request/response based environment
     • Why the Dispose/Finalize methods are so important and how the GC works
     • How your computers memory and general IO works
       
       And you are not interested in finding out, then to be quite blunt - stick to small websites!
        
   • Learn why you should split Presentation from business logic and business logic from data logic. 
   • Get Lutz Roeder’s Reflector and don’t be scared to use it to view the internals of .NET. You may be surprised what you find and how it will improve your ability to leverage .NET.
      
4. Be your own apprentice.
   1. Buy books and learn.
   2. Use gained knowledge and help others
   3. Goto point a - Repeat forever.

** I have added this here as this is a subject that I discuss and work with often. 

The original post can be found on this thread: 

SitePoint - General Dev Issues/Difference between Web & Software Development . **

(and various others… but the above encapsulate most of it)

In the days of yore, developing interactive non-static web applications tended to be the province of C++ developers via the CGI standard of the HTTP protocol. This required an in-depth knowledge of communications and the servers OS. Later this progressed to Perl implementations which started to allow abstraction of the hardware layers from the implementation allowing greater productivity. However Perl as a language suffers somewhat from a geeky image and never really got the popular vote.

It wasn’t until PHP, ASP and their ilk that web development started to come to the masses. ASP (with VBScript/JScript) and PHP are both exceptionally well abstracted from the hardware and only require a superficial knowledge of the underlying systems to be productive. Due to this, pretty much anyone who could string together an if statement and understood basic algebra could start creating dynamic websites.

More recently this is beginning to change again. Websites are beginning to look and work like applications (SaaS is a good example of the future) and the distinctions between Web and Desktop applications are beginning to blur. Developers are being required to have more than a superficial understanding of the hardware and systems they are using and this is actually beginning to become a problem that business is starting to notice.

The cohorts out there are beginning to mostly polarise into around four factions.

• Designers who became web developers who stick to their preferred technology (e.g. PHP/ASP) no matter where it takes them
  
  These individuals are usually those who are self employed or employed by smaller firms. Most of the larger corporations are beginning to ignore this group as many see PHP and ASP as inadequate.
   
• Designers who became web developers going back to near pure design.
   
  This is by far the most common route for an ex-designer. These designers are quite sought after by the larger corporations as they at least understand development work, and can even work on client-side scripting.
   
• Developers who became web developers who stick to their preferred technology no matter where it takes them
   
  This group is beginning more and more to be seen as specialists or more often as outmoded and unemployable. Most employments in this area now are becoming contracts or outsource roles (see point 1). Most developers who did this are widely (and possible erroneously?) considered to be individuals looking for an easy life in their day to day work.
   
• Web developers or developers who became web developers going to near pure software development OR moving into SaaS, SOA and related technologies.
   
  This is by far the most common path for developers, although those coming from web development backgrounds are finding the path harder as they have to re-learn and work around mistaken perceptions generated from their PHP/ASP pasts. Those coming from a more non-web background but moved into the web arena are the best equipped and the most sought after.

In basic conclusion to the question

In essence no, a software developer is a software developer, web or otherwise. However, if you consider ‘Web Development’ to be different from ‘Non-Web Development’ then historically yes, there is a difference, one that is beginning to blur.

A few years ago, Web Developers generally required less technical knowledge. Although the larger the system being developed, the more technical knowledge required, and coincidently this seemed to tie hand in hand with a scale that went like this:

The smaller a system, the more PHP, ASP and their ilk was used.
The larger a system, the less PHP, ASP and their ilk was used.

As applications got bigger, COM/COM+, Java and more recently .NET got used more, and this requires much more technical knowledge than that required to create a site using PHP, ASP and their ilk.

These days as ASP.NET and equivalents are taking their share of the web, higher skill levels are required if you want to go beyond the productivity basics supplied by their respective vendors.

As always there is the question of scale, with scale come’s complexity and that’s the basic truth of it.

Much of my work more recently has been to do with repair. It is an unfortunate trend that businesses and technical teams underestimate the cost and requirements of using the newer technologies and they can easily become out of their depth.

Teams who have happily worked for a decade with the script based technologies with a smattering of back-end components have been rudely shocked by the differences when attempting upgrades. Unfortunately there is also a growing number of developers who are amazing with the older web technologies that are beginning to flounder, and it’s a sorry thing to see – especially in the UK where training is a rare commodity.

As a personal view therefore I must say that yes, there is a difference and it costs business a lot money. Hopefully time will remove those differences.

- Matt 'Moridin' Warren