What top .NET Technologies for .NET Technical Lead Role?

curiouswebster
curiouswebster used Ask the Experts™
on
What top .NET Technologies for .NET Technical Lead Role?

I am brushing up on various .NET Technologies to fill a  .NET Technical Lead Role which will involve not only various technology choices, but mainly the communication with a global team of developers who need to implement these technologies.

So, please provide me a list of .NET Technologies which I should prioritize as I spend the next few weeks ramping up.

I may also be looked at to assemble a list of coding standards (coding do's and don't's), then to use code reviews, pull requests, etc. to help communicate those coding standards to a team, some of which may be an offshore and on a different timezone.

So, can you start with a short list of .NET technologies that can prime the pump and get my juices flowing again with these topics, most (or all) I have worked with previously in some capacity.

Thanks.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Commented:
This is going to sound harsh, but the point of a lead role is that the person in it is the one who should know these things already. If you're asking for this stuff, then I would caution you against taking the job.

Think about it - what happens if you can't meet the employer's expectations? You end up getting fired because the end results of your deliverables are cobbled together using some knowledge of C# and a bunch of code snippets found through Google. That kind of thing is perfectly fine for a non-lead role. It's how you learn and groom yourself to go into the lead role. But it's not good quality for a lead role to produce, and getting fired is not a good thing for your resume.

That's my advice to you. Moving onto concepts that a lead role should know (my opinion):
- WCF - consuming and creating web services
- SOAP vs. REST
- Crypto and SAML (e.g. PKI, symmetric encryption, HMAC hashing, etc)
- How common protocols work (HTTP, HTTPS, SMTP, LDAP, etc)
- WPF and Winforms
- Threading and locking (e.g. syncroot patterns)
- Data binding
- Major database types (MySQL, Sqlite, NoSQL, etc) and best practices (how to optimize queries, indexing, stored procedures, etc)
- basic IIS
- Sessions (for web)
- Memory management (e.g. avoiding memory leaks from event subscriptions, idisposable, managed vs. unmanaged code, data type optimization, etc)
- Serialization (XML and binary at minimum)
- Common I/O (e.g. streams, reading a file in chunks, when to use String builder, etc)
- Reflection
- Debugging (breakpoints, conditions, watches, etc)

I would expect any lead .NET person to be very comfortable with all of these topics. Some of them are huge areas (e.g. WPF and XAML).
curiouswebsterSoftware Engineer

Author

Commented:
Thanks for the answer. It is a lead role, but it's mostly about working with an offshore team and organizing work. In the interview, I was deemed "technical enough" since it is all about team building and organizing.

So, I will have experts on the team and will not be the architect. I will get through it.

It's mainly about MVC, ASP.NET and SQL Server. They did not mention any of the other technologies you mentioned. But they did talk about communications skill as being paramount.

You gave me a good list of things I have only had some exposure to and it'll come in handy.

Thanks.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial