For some time, I have been thinking about language contructs that are a pain when it comes to code management, readability and more often than not inculcate poor coding habits amongst developers.

• Nested classes -I have never found a valid reason to use them. I really feel that an inner class is something that looks better in books and asked in interviews. I haven't noticed a single instance where you *really* need a nested class. I am sure there are better, much more readable ways to code.
• params - One can easily go with a collection/DTO which holds the required parameters. It is a just redundant. If I do not have the exact number of parameters that a function I write expects, I would use an array, like its done in a BeginInvoke call for a Control instance
  public virtual IAsyncResult BeginInvoke(
     Delegate method,
     object[] args)
  

     Morover, If I ever use more than 10 input ( + output ) parameters, and not think about a DTO, I would better stop programming and start afresh on alchemy (not a bad idea either).

There is goto but I will never let go of it, reminds me of better times ( jmp is still there at the top, and will remain), even though I prefer not to use it.  

   Now with 2.0 comes another new one. partial classes. The documentation more than tries to please the reader and clearly indicates that this is really needed for Code generation, Windows forms underlined. There is a problem here, not only is it *not needed*, it is powerful enough for a set of developers to develop a bad habit, rather than code. Ofcourse there are better ways to hide generated code, XAML +/ inheritance (as with ASP.Net web-pages) for designs atleast, or arent't they?

Two developers maintaining a class is a maintainance problem, three is a disaster. And partial interfaces ?