Which knowledge should any C# developer have?
Question is posed: which knowledge should any C# developer have? Basic knowledge anyone should have without exception, Advanced knowledge, Expert knowledge etc. No need to go into details.
Our opinion, C# developer should have the following knowledge:
- and generic collections
- Garbage collection: when should you call GC.Collect (hint: pretty much never) and why.
- Be able to answer some easy questions on specific common classes in the .Net BCL: namely from System.Data (think parameterized queries!) and System.IO (filestreams, path).
- Comfortable explaining some basic concepts from at least one of winforms, wpf, webforms, or MVC
- Have used anonymous delegates / lambdas in at least one project, and therefore also have a basic idea about closures.
- Overview of threading concepts (same as xml/serialization). Bonus points for understanding why most thread-safe collections aren’t.
- Overview of Xml in .Net (same as serialization)
- Overview of serialization in .Net (maybe not have done it, but understand what it is and know where to look in the namespace heirarchy and documentation)
- IEnumerable: including common extension methods, iterator blocks, and deferred execution
- IDisposable: how it’s integrated into the language and why
- Interfaces (specific), namely –
- Interfaces (general)
Please feel free to mail us at ntp.interview@gmail.com if you have questions or comments. Visit site at http://www.interviewquiz.net/ for updates and more information.
No comments:
Post a Comment