poltr1: (Default)
(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.)
poltr1: (Marcus scowling)
Not so many years ago, there was a shortage of computer programmers here in America. We were dealing with the Y2K problem at the time. So we opened our doors to immigrants from other countries who had talent in computer programming and software development. And thus, the H-1B Visa program was born. It was a good idea at the time.

In 2000, I worked on a program for a client that tracked engineering drawings and reminded them (and their managers) if a drawing was going to be late. Two years later, I'm told that a team in India will be taking my code and re-writing it in Java to be used business-wide, and that I would not have any involvement in the effort, other than the notes and code I already provided. At the time, I thought, "Great for globalization and the bottom line. Not so great for American programmers."

Somehow, the idea that companies can offshore their software development to people in other countries became all the rage. Why pay an American programmer to do the work when someone overseas can do the work for less than half the price?

And here it is, 2011. The American economy is in a recession, has been for the past few years, and may very well be on the verge of depression. We appear to have a glut of computer programmers now. So why are companies keeping American programmers like me out of work? (I can't be the only programmer in this situation.) Because the folks from overseas are still cheaper than I am, and may be able to do the job better than me because they're trained and experienced with the new technologies that are in demand.

So I'll ask: Is it time to retire the H-1B visa program? Or do we need to curtail the amount of foreign workers that come to America every year?

Or am I way off-base on this one?

Profile

poltr1: (Default)
poltr1

May 2025

S M T W T F S
    123
45678910
11121314151617
1819 2021222324
25262728293031

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 12th, 2025 10:28 pm
Powered by Dreamwidth Studios