![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Entry tags:
C# and .NET.....
(Originally posted to my Facebook wall.)
How difficult are C# and .NET to learn? I see lots of job opportunities that ask for those skill sets. But since I never worked with them, I wouldn't qualify for those jobs.
As I understand it, C# is Microsoft's "answer" to Java. Years ago, Microsoft had a language called Visual J++. Rather than have a "pure" version of Java, they put their usual "innovation" spin on it. A judge told them they couldn't do this, that it was too close to the original Java language. So, add some more syntax changes and viola! A new language. Us techie types know there isn't much difference between the two, but to HR people and hiring managers, they're apples and oranges.
.NET is, I think, some type of library of callable routines. Years ago (1999-2000), I worked with Visual C++ and MFC. Even after six months, I was still referencing the MFC manual. That told me, "You still don't know the code." I think .NET is an extension and/evolution of MFC, but I wouldn't know.
If I had good reference materials for C# and .NET, along with existing code to look at, I could write decent code with them. But again, I run into the old "no experience, no job" wall.
I never cared much for Microsoft's software engineering practices. Or lack thereof. As far as I know, they still don't have a roadmap to CMMI Level 5 compliance. I suppose they're content with producing "average software for the average user". (Yeah, my bias is showing. I much prefer the open-source bazaar to the proprietary cathedral.)
How difficult are C# and .NET to learn? I see lots of job opportunities that ask for those skill sets. But since I never worked with them, I wouldn't qualify for those jobs.
As I understand it, C# is Microsoft's "answer" to Java. Years ago, Microsoft had a language called Visual J++. Rather than have a "pure" version of Java, they put their usual "innovation" spin on it. A judge told them they couldn't do this, that it was too close to the original Java language. So, add some more syntax changes and viola! A new language. Us techie types know there isn't much difference between the two, but to HR people and hiring managers, they're apples and oranges.
.NET is, I think, some type of library of callable routines. Years ago (1999-2000), I worked with Visual C++ and MFC. Even after six months, I was still referencing the MFC manual. That told me, "You still don't know the code." I think .NET is an extension and/evolution of MFC, but I wouldn't know.
If I had good reference materials for C# and .NET, along with existing code to look at, I could write decent code with them. But again, I run into the old "no experience, no job" wall.
I never cared much for Microsoft's software engineering practices. Or lack thereof. As far as I know, they still don't have a roadmap to CMMI Level 5 compliance. I suppose they're content with producing "average software for the average user". (Yeah, my bias is showing. I much prefer the open-source bazaar to the proprietary cathedral.)
no subject