Slashdot Mirror

← Back to Stories (view on slashdot.org)

.Net Programmers Fall in CNN's Top 5 In-Demand

Posted by Zonk on from the cha-ching dept.

GT_Alias writes "CNN Money is reporting that .Net programmers are one of the top 5 most in-demand jobs. Of the positions where recent surveys have indicated a labor shortage, .Net developers and QA analysts are the two that fell under the 'technology' category. According to CNN Money, .Net developers can make between $75-85K starting out in major cities, with the potential to make 15% more if they have a particular proficiency. Additionally, QA workers can make $65-75K a year with the ability to negotiate a 10-15% pay jump if they switch jobs. How does this information compare with the Slashdot crowd's real-world experience?"

46 of 602 comments (clear)

  1. Large groups of employers by eneville · · Score: 3, Insightful

    Never underestimate the stupidity of large groups (the employers) of people. .net is just a freaking platform, its not like it is anything special, just another language that just depends on different things. Offers very little that most other languages offer in much the same way.

    Why isn't something that's more portable (perl/python) in such demand? Really bakes my noodle.

    --
    Why UNIX?
    1. Re:Large groups of employers by Erik+Hensema · · Score: 3, Insightful

      Because .NET is the major development platform of the major operating system.

      Neither perl nor python are very popular for large application development, even on unix. So there isn't much demand.

      --

      This is your sig. There are thousands more, but this one is yours.

    2. Re:Large groups of employers by lilnobody · · Score: 5, Insightful
      Why isn't something that's more portable (perl/python) in such demand? Really bakes my noodle.


      Ever try and write an enterprise level application, even a web application, in perl? It's great for small internal applications; that CPAN doo-hickey works just great.

      But CPAN bites you back when you hit the limits of what those modules can do in a large-scale application. When you hit the limit of what is the easiest and arguably the best (and arguably not) ORM out there, Class::DBI, there's 150 different, incompatible modules out there to do what you want. Which one will be maintained? Which one silently overwrites methods deep within more established modules and doesn't tell you? Want one that adds support for limit and sort by? One module gives you that easily, but not with the same interface as the other 10 that are more full featured. Which do you choose?

      Don't even get me started on trying to send an email with Perl. CPAN seems to have a new module for sending email every other day. It's become less of a one-stop shop for the modules you need and more of the perl newbie ftp drop site for modules no one could possibly need or want.

      As an example, check out what's been uploaded today. Version 0.02 of JavaScript::MochiKit, helpfully described as 'makes perl suck less', with 15 classes and less than a page of documentation. Great! Just what I was looking for!

      There's also a module for interacting with MySpace, two versions in the same day of of an XML parser (writer? who knows, I didn't read it) for a data format used by the library of congress (from the same proud author of version 0.3 of Acme::Voodoo, described as 'Do bad stuff to your objects'), version 0.18 (version 0.17 was yesterday's) of DBIX::Class::Loader, a copycat of Class::DBI::Loader for this self-proclaimed CDBI replacement (which is probably needed, but god help a perl newbie who shows up on CPAN looking for ORM nowadays). It's 2pm my time (Austria), meaning it's 5:30 central time, and there are already 9 modules with version numbers less than 1.0 uploaded to CPAN.

      Now don't get me wrong, this is fantastic for a small scale app. I'm sure someone will get some use out of a MySpace profile accessor in perl. But what makes CPAN, and perl, great for small-time stuff makes it just terrible for enterprise applications.

      As for perl's portability...do you really expect to make an argument that a language that is, in quite official terms, defined by the official compiler is portable? Perl runs on windows, but since perl.exe IS the language, differences between it and the unix versions aren't even technically bugs...they just ARE! It's not a proper way to 'run a language', so to speak.

      I've been programming in perl for years. I get paid well for it. I don't plan to stop using it for my insignificant applications. But I know damn well why it's not in demand.

      nobody
    3. Re:Large groups of employers by NutscrapeSucks · · Score: 2, Insightful

      Hint: Trying to judge the software development market based on your Debian installation is futile.

      Perl -- Had a shot at commercial app dev relevance in the 90s, but the world passed it by, and is used rarely for new projects. Largely relegated to Unix system scripts, which is more of what it was designed for.

      Python -- Just because some college student coded a filesharing app with it doesn't make it a popular language. Nothing against the language, just that you probably won't find a job using it.

      IIS -- it's actually a very popular web application server, but very few of those installations would show up in Netcraft surveys because they aren't Internet-accessible. Judging by the job market it's much more likely you will be "working" (that is, getting paid) on IIS or even Tomcat rather than Apache httpd.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    4. Re:Large groups of employers by Anonymous Coward · · Score: 1, Insightful

      On another note, I can't count the number of time I get called in to fix a Windows install at an SMB. This is weeks after they buy their MS SBS 2003 and have their tech genius (the boss knows Komputors!) install it.

      All they want is a file server and email. So they spend 5k on a server and 3k on the software and some licenses for their 10 computer company and *all* they want is shared drives and email. Literally.

      So I come in, clean up their Windows install. Configure their machines. Make things work.

      Could be done with Linux and free software for ... what? Cost of server and me coming out? Actually would take about 1/2 the time to install and configure. Save 3k. Seems like a good idea to me.

      But hey, Windows is great for my wallet.

    5. Re:Large groups of employers by Decaff · · Score: 2, Insightful

      Hint: Trying to judge the software development market based on your Debian installation is futile.

      Heh. This sums up so much about posts on development languages on Slashdot.

    6. Re:Large groups of employers by nobodysbusiness · · Score: 2, Insightful
      Neither perl nor python are very popular for large application development, even on unix. So there isn't much demand.
      This may be changing. I've been interviewing with two companies recently, and they both either use, or plan to use Python for a major application. On one hand, the first company sells a Windows Server 2003 box with MS SQL 2005 and Python for the backend to their app. The client software? C# and .NET. The second company is selling a server running Fedora Core 4 and PostgreSQL, with C++ as the main language. However, they have began to recognize productivity problems, and are therefore planning to wrap their C++ core in Python or some other Very High Level Language (VHLL). Get used to it folks. In the future, most software will be written in a VHLL, with a few performance critical sections ported to something like C++ or C#. Sound familiar? Thats what people used to use assembly for. PS: First post
    7. Re:Large groups of employers by Anonymous Coward · · Score: 3, Insightful

      I have worked on large scale Perl applications. The key ingredient is intelligent programmers. Sadly many companies do not realize that spending 150K per person on two programmers is more efficient than spending 85k per person on 10. Companies would rather have lots of monkeys than a few geniuses. Syntactically restrictive languages are popular because of this. ORM mapping modules are more necessary in languages that enforce OO programming. I would rather be able to use more powerful techniques when appropriate. And I would rather work on a large Perl project built by a few smart people than a large java/.net project built by a tide of idiots.

    8. Re:Large groups of employers by pooh666 · · Score: 2, Insightful

      Wish I had mod points for you. There is always a clue to such posts as your parent, things like, complaining about sending emails. So Net::SMTP was really hard to find? You have to know the modules and tools people write in Perl just like with anything else. But with Perl it is quite easy to fix the damn thing yourself. Recently we were building a home spun(for very good reason) webmail app. The use of Email::StripMIME save massive amounts of time and worked very well. When we found a bug, we worked around it and sent an email to the author. We are now handling hundreds of mail accounts with hundreds of thousdands of emails and doing quite well. The sad part is that not many people seem to understand what you and I do about Perl. But a few do, one great example of a LARGE app that I know of is Bricolage.. Which is getting cooler all of the time, now support PHP templates.

    9. Re:Large groups of employers by lilnobody · · Score: 4, Insightful
      Ahh, a common confusion. You have confused respect for the language with respect for the needs of a long-term, well-designed system. I'm responding to two posts at once here, which I think is fair since one wishes he had mod points for the first, so please bear with me.
      The key ingredient is intelligent programmers. Sadly many companies do not realize that spending 150K per person on two programmers is more efficient than spending 85k per person on 10.

      This is exactly why .NET is in demand and perl is not--the focus of the story. Note I never said I was going to stop using perl. Putting aside the problems of finding those two people to design an application, you then have to tell a client that 50% of your design team can be hit by a bus tomorrow, and it's just not what people want to hear. Enterprise projects are not about efficiency of development. Enterprise projects have completely different goals, and that's what most perl programmers fail to understand.
      And I would rather work on a large Perl project built by a few smart people than a large java/.net project built by a tide of idiots.

      This attitude is exactly why the perl culture is not going mainstream. This is the attitude of someone who refuses to work with a team that hasn't forced him to respect them. This is how primadonnas think, and not the way the people who have those .NET programming jobs at good salaries want programmers to think.
      There is always a clue to such posts as your parent, things like, complaining about sending emails. So Net::SMTP was really hard to find? You have to know the modules and tools people write in Perl just like with anything else.

      This misses the point of my original post. I never said I couldn't find a tool to send an email. I said that CPAN is a clearinghouse for unfinished, in development, and first-time libraries. Net::SMTP does in fact work rather well. I've used it. But, say I were showing up to CPAN the first time. A search for 'Send Email' (most people are thinking about emails, not SMTP), brings me to Email::Send, Email::Send::Sendmail, Email::Send::NNTP (this doesn't make much sense), Email::Send::Qmail, Log::Dispatch::Email, Test::Nightly::Email, Mail::Spool, Mail::Sender, Mail::Sendmail, Mail::Send, Mail::SendEasy, and there are even more. This is ridiculous; it would be impossible to make a business justification for choosing one over the other.

      Compare this to the MFC, which, while not NEARLY as extensive as CPAN, is MUCH better documented, is standardized, and it's a safe bet.
      When we found a bug, we worked around it and sent an email to the author.

      Why not just use the MFC and write your own, if you have to pay attention to the guts of the library code? A business wants to be able to say: we can be SURE of our library code, and we wrote everything else ourselves.

      I'm not trying to say it's better or worse, the whole perl culture thing. It can be quite good, actually, and I think other language communities should take a hint from perl in some areas, especially some of those libraries which arose out of the system I am so quick to disparage. There should be something as good as DateManip in every standard library, and Date::Simple lets one use dates almost as easily as a primitive, which makes life SO much goddamn easier, to be frank. I understand that perl has definite advantages.

      But that is just not what a business is looking for. Both of the parent posts to this smack to me of elitism. That perl is better than some other language for some reason. It's not the language. It's the culture surrounding it. It is, no offense, people like yall who think that management is stupid for going with the trend. Software is a means to an and, and not a means unto itself. The tools for creating a tool, by and large, should not be out of the ordinary.

      nobody
    10. Re:Large groups of employers by typical · · Score: 2, Insightful

      ...and we wrote everything else ourselves.

      A sure sign of quality. :-)

      --
      Any program relying on (nontrivial) preemptive multithreading will be buggy.
    11. Re:Large groups of employers by Prof.Phreak · · Score: 2, Insightful

      Neither perl nor python are very popular for large application development, even on unix. So there isn't much demand.

      Are you kidding?

      Besides for Microsoft shops (relatively new development), most of the industry (any company with IT department older than 20 years) uses UNIX (and a fair bit of Perl/shell/C) for their core business. I'm not talking about employee computers (all those are Windwos), but servers, databases, etc., stuff that folks actually maintain/write code for.

      When I hear of a corp using MS SQL Server and MS software for everything, that basically tells me that they've only been using IT in their business for the last 5-7 years. (again, I'm not talking about employee computers).

      --

      "If anything can go wrong, it will." - Murphy

  2. Re:Kill me...kill me please. by Musteval · · Score: 2, Insightful

    There's a shortage of blind monkeys missing three fingers that want to learn these languages.

    Anyway, just because it's easy to learn doesn't necessarily mean that it's a bad programming language. It just means that it's an easy to learn one.

    --
    Note to mods: I'm probably being sarcastic.
  3. Re:Kill me...kill me please. by jimicus · · Score: 5, Insightful

    Anyway, just because it's easy to learn doesn't necessarily mean that it's a bad programming language.

    No, but sooner or later it means that there are a bunch of colleges churning out people who've become "experts" having taken a 6 week course in the language with no prior IT experience.

    Doesn't take long for it to become apparent that so many people who claim to know the platform are inexperienced fools. Once that happens, salaries drop.

  4. Better: be wide-minded by faragon · · Score: 5, Insightful

    As rule of thumb, may be it is better for you to invert in general Computer Science formation (generic OS, compiler understanding, computer architecture, algorithmic complexity, et al), not just the "follow the last wave formation". Most people doesn't ever consider that it is dangerous to be extremely especialized. This applies to any platform-specific developing environment.

    In the long way, you'll have to switch between many OS, compilers, languages, etc. Sometimes you have to be pragmatic, just to pay the bills, but take conscience about that the IT field is very variable in the surface, but sound in the fundamentals. This is why I recommend generic Computer Science formation when young people ask me for an advice (plus some other "last wave" preparation, just in case).

    1. Re:Better: be wide-minded by the+eric+conspiracy · · Score: 2, Insightful

      become a plumber...

      And spend the day cleaning out other people's shit? I don't think so. Not to mention that the pay is NOT as good as programming, and programming skills can be leveraged into better jobs. I did a career chance from another engineering field into programming - after 3 years of coding I am now a JOAT leading both a development team and a research team.
      of

      In 10 years all the programming jobs will be outsourced to India/China

      Not hardly. Outsourcing is slowing down.

      The safe rule: get a great education, heavy on the math, develop your writing skills and the world is your oyster. Even though I never had a formal course in computer science I can solve problems none of the computer science people I work with can touch because of the math I can do.

      Math is the universal key.

  5. Re:Kill me...kill me please. by Silverstrike · · Score: 5, Insightful

    Will someone please explain to me why syntactical ease equates to a "stupid language for monkies"? Just because C# developers don't have to worry about and juggle memory pointers, it doesn't imply that their job is automatically "easier" and therefore "worse" than that of a C/C++ developer. They still have to worry about good OO design, portability of code (yes, even in a VM language like .NET), and just all around good software engineering -- same as a C/C++ developer would.

    Furthermore, just because C/C++ is a "faster" language, that doesn't imply its better suited to web development, or even windows app development. A strongly typed language with a predefined API like the .NET Framework gives everyone an even playing field -- it makes code extremely supportable by a wide range of people; everyone who knows .NET can support an app written against the Framework. Not so for C/C++, a windows/Visual Studio C++ developer would certainly struggle after being tossed into a Unix development environment.

    Now, this is the same argument as most people with common sense make with Java -- no on says its the right tool for every job, but it certainly can be the right tool for a lot of jobs. The same with C++. Do you really think we ought to code our web apps in C/C++? IF so, then why not just go all out and do it in assembly?

  6. Why .Net? by el_womble · · Score: 5, Insightful

    I'm in the (un)fortunate position of seeing .Net and J2EE being used sideby side in the same application, and I don't get why people are using .Net in the enterprise. It can't be because CLR is faster than the JVM, it isn't. It may be fair to say that, for a bog standard application, .Net development is faster (Visual Studio is an excellent tool), but as soon as you start to push its framework (as all real applications do) the .Net teams fall behind the J2EE teams.

    Java gives you choice. Choice of IDE, choice of framework, choice of application server and perhaps most importantly choice of platform. All that and it runs as fast as .Net and, if your on a budget, everything can be got for free. Need support? Buy WebLogic or JBoss support. Need training? Sun are more than happy to oblige. Need developers? You can't spit without hitting a J2EE developer. Need the source code? Sun will hand it over, for free, just don't expect any changes you made to be put back into the source tree, or them to give you any slack if you try and distribute at all - its not the freedom that OSS would like to give you, but its better than .Net.

    So is it any wonder that there are less .Net developers. If I was starting out in software development again, I'd be still be looking to start in Java, and expect to move over to Ruby on Rails (or whatever is flavor of the month) in 5 to 10 years. Assuming people who make IT descisions get smarter, and OSS continues to get stronger, I can't see how any company selling enterprise grade software will be selling anything but the time and experiance of their staff sans the licencing fees of the tools and server software to their customers. How else will western developers compete with China and India?

    --
    Scared of flying, pointy things snce 1979!
    1. Re:Why .Net? by azaris · · Score: 3, Insightful

      So is it any wonder that there are less .Net developers.

      More likely the story is that the old Windows developers are clinging to VC++ and VB instead of making the transition to the new .NET languages. Many of these .NET jobs are probably converting legacy Windows apps to the .NET platform. You can't just throw away a codebase worth years of labor and start over with Java, PHP, Ruby on Rails, or some other buzzword compliant flavor of the month.

      I know we have to deal with this transition at work, so probably many others will have to, too.

    2. Re:Why .Net? by shutdown+-p+now · · Score: 3, Insightful

      If you want to switch IDEs, operating systems, and whatnot, then, indeed, Java is a better choice. But in many cases you just don't. The whole thing with .NET is that it works really nice in its native environment (which is Windows/IIS/MSSQL). There is a level of integration there between libraries, components, and tools that Java simply cannot afford (due to its cross-platformability). This is not to say that .NET is locked into this particular environment - you can use Linux/mod_mono/MySQL, for example - but it just won't give any advantages over existing solutions then. For MS shops, however, .NET is a blessing - and there are plenty of those.

    3. Re:Why .Net? by gh · · Score: 5, Insightful

      I agree with the other poster. This never should have reached a +5. Not only is it off topic, but the arguments are weak.

      It can't be because CLR is faster than the JVM, it isn't.

      The performance of the two runtimes are comparable. Neither kicks the other's butt. Like all things, you can find a benchmark that proves one is better than the other. At the end of the day, the apps that both Java and .NET are being used to write, performance is not going to be the reason you choose Java over .NET or vice-versa. You'll see a bigger performance gain if you simply design the right architecture for the platform.

      as soon as you start to push its framework (as all real applications do) the .Net teams fall behind the J2EE teams.

      I would beg to disagree with this statement. Personal experience has dictated the exact opposite. But, it would help if you provided an area where you feel .NET falls down. Otherwise, it just comes across as someone who keeps spouting the /.-think that Java is better than .NET soooo nyah!

      Java gives you choice. Choice of IDE, choice of framework, choice of application server and perhaps most importantly choice of platform.

      All that choice, as someone else pointed out, can be confusing. If you're building an application for an enterprise system you want to know what will get the job done. Not only that, but you want to know that it will be supported in a meaningful way down the road. The fact that Java has hundreds of frameworks (most of which duplicate functionality of other previously written frameworks) is actually a disservice. It's the old "jack of all trades, master of none", but applied to frameworks. The frameworks also mimic the fashion/pop culture than being technical solutions. This week it's struts, next week velocity, the following week some other framework. Enterprise solutions prefer solid choices, not the fad of the week.

      You could make the argument that if the framework is open source, then you are guarranteed to have the framework down the road. But, that involves getting into the code and supporting the codebase. If it's critical to the company's environment they will do that regardless. In fact, likely the would have written/extended most of it themselves. The thing is that most of these frameworks are *not* critical in the "it gives us a market edge" sort of way. It doesn't make business sense to drain limited resources by supporting a toolset that turned out to be a fad and not properly supported down the road.

      and expect to move over to Ruby on Rails (or whatever is flavor of the month) in 5 to 10 years

      And that, dear /. poster, is exactly why many platforms like .NET do well in enterprises when compared to the many flavors of tools from the other platforms/communities. It's not that .NET (or Java for that matter) is miles above the rest in terms of technical superiority. It's simply that .NET offers a solid platform that business can depend on without wondering is this simply the flavor of the month.

      Despite what most /. posters think, Java was successful for the exact reason .NET is becoming successful. The platform serves as good foundation for building applications that can be supported many years down the road. Think of it as what COBOL use to be for business. It's not the choice that Java presented, but a solid API and platform that will be built upon and supported by big players like Sun and IBM. That doesn't mean the choice isn't important in many cases, but in the grand scheme of things it's minor.

  7. Re:I'm Job Searching by CastrTroy · · Score: 5, Insightful

    You should just buy a book and learn it yourself. Do some real projects that you can demonstrate to the interviewers if you don't have any real world experience. You can use Mono if you want, or use the VS.Net Express Edition to get started. Once you get into more complex stuff, it'll probably be better for you to get real experience with the real VS.Net IDE. It's a pretty powerful IDE, and I like it a lot. There's a few things I'd like to change, but otherwise it's pretty good.

    --

    Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
  8. Most of you are missing the point... by Anonymous Coward · · Score: 1, Insightful

    Yes you will make those salaries.. IF and only if you have the background and years of experience.
    By background i mean 3 thiered knowledge, application life cycles..etc
    and have a few large corporate project behind you.

    Don't think for an instant you will get those amount of dollars for just
    knowing VB,C#,ASP.net

    Same applies to any language btw.

    My advice is this, start small, get good projects that has the potential to be completed behind you and build up on that, your position will evolve naturally into corporate type programing in no time!

  9. Re:.NET? Who cares? by Rich0 · · Score: 2, Insightful

    I'm sure Windows will be with us for a long time, but I'm also pretty sure that .NET won't.

    Remember COM+, ActiveX, etc.? Every 3-4 years Microsoft comes out with their latest interfaces, buzzwords, etc. In a few years MS will be moving from Visual Fred to Visual Jake, and everybody will be doing backflips to migrate their legacy code.

    Is it time to retire some of those COBOL/CSIS mainframes? Sure.

    Do we need to rewrite every application we own just because it is more than three years old? No...

    A lot of shops still have VB6 sitting around because of the large number of difficult-to-port applications. How many people have GCC v2 lying around for hard-to-compile C apps? Almost none, since the GNU folks are half-decent about backwards compatibility in their development tools. When things break it tends to be minor - as it should be for a programming language.

    The bottom line is that programmers shouldn't have to jump through hoops every time MS wants to sell more development stuido licenses, or needs to attract media attention...

  10. Web RAD by NutscrapeSucks · · Score: 3, Insightful

    Aside from any of the language issues, ASP.NET provides a really productive environment for web app development. At least for projects of a certain size, ASP.NET is much cheaper/faster to develop for than J2EE, and the resulting code is generally pretty clean and easy to maintain. Java has all this heavy infrastructure for large applications (Struts, Spring, Enterprise Beans), but result is that it's uncompetitive for the small-to-midsized ones.

    --
    Whenever I hear the word 'Innovation', I reach for my pistol.
  11. Re:I'm Job Searching by ACNSlave · · Score: 5, Insightful

    I would be ashamed to be a *dot* net programmer. Use Debian or similiar distro, and you can get programmers from all over the world.

    Meh. Shame has nothing to do with it. Feeding 3 kids, paying down a mortgage and putting gas in my Saturns has much more influence over me than your philosophical bullcrap. Shame... What Ever.

    Final analysis: code is code is code. If coding for OSS projects floats your boat, then do so, Its a free world. I use Debian too, just not @ work.

    BN, MCAD .NET (C# corporate whore)

    Cheers, my man

    --
    Today is a good day to code.
  12. Re:I'm Job Searching by Anonymous Coward · · Score: 3, Insightful

    This is actually a crap shot. If you are just starting, do not lock yourself into one thing or another. Keep in mind that there are plenty of MS coders out, many who are currently unemployed (with more coming). In addition, if you read the article, it is for EXPERT .net coders (i.e. with 5 years experience). What was missed is that experienced *nix coders typically make 100K and above (also with 5 years experience or more).
     
    While you should learn this, you should also be gaining experience in java/C/C++, php, ruby, maybe some cobol and VB, and on several platforms particularly, Windows, *nix (apple and linux are the most used *nix, but solaris is big in some companies and you can also download for free).
     
    Personally, I woudl try to judge the market and ask what will be hot in about a year, not what is hot NOW!. Then shoot for that market. For me, back in the mid 80's, I did trs-80 in a lab as well as mainframe/dos/apple, then in late 80's, I started down the path of network coding on Unix, moved on perl/web development in the early 90's (with the real jobs of working at IBM Watson(OS2/AIX), HP(HP-UX), Bell labs(Windows/SunOS) and USWest (mainframe, apple, HP)), started Linux coding in 93 with jobs in 94 through 97, teaching for the next few years (working on start-ups doing wifi), now contracting to move stuff from WIndows to Linux (lots of calls for that).
     
    Make the right call, and you have plenty of work. Make the wrong call, and you are unemployable.

  13. Re:Kill me...kill me please. by CaymanIslandCarpedie · · Score: 5, Insightful

    Wish I had mod points! Exactly correct, langauge really means nothing and I find this lists about as worthless as can be. Technology changes fast enough as it is, you don't need to make it worse by spending your career constantly chasing around the "hot" new programming language hoping you'll make a few extra grand a year!

    Rule number 1) gain a solid understanding of computer, programming, design, network fundimentals. I doesn't matter if its Linux/Windows, Java/C++/.NET, etc, etc.

    Once you have this solid foundation to build on then decide what industry segment you'd enjoy working in and learn that business segment inside and out.

    I know as techies we often don't like dealing with getting our selfs "dirty" dealing with the business, we just like the tech but that will lead to a frustrating career in my opinion. Programming is becoming easier and easier, there is getting to be less and less value in being able to program any certain langauge, you can spend you entire life jumping between industries chasing the a few extra bucks in the lastest langauge or become an expert in an industry (where the real money is). When I'm looking to hire someone I couldn't care less what languages they know! As long as they are decent programmer its easy to teach them a new langange. Whats much more difficult is teaching them the fine points of our industry. So be it finance, retail, manufacturing, gaming, ect, etc. I think knowing a busniess well is much more important than what langauge you know.

    --
    "reality has a well-known liberal bias" - Steven Colbert
  14. Re:Yes! They're Right! by NutscrapeSucks · · Score: 4, Insightful

    Care to explain how a "bondage and discipline" language like C# is easier to learn and more tolerant of bad programming practices, than TMTOWTDI open source languages like PHP and Perl? Oh, that's right, you were just spreading FUD.

    For years, one could blame Microsoft for cheap amateur hack coding. No more -- Open Source "LAMP" now totally owns that market.

    --
    Whenever I hear the word 'Innovation', I reach for my pistol.
  15. Re:I'm Job Searching by GiantCranes · · Score: 3, Insightful

    There are many great resources available for you. Grab yourself a copy of Visual Web Developer Express: http://msdn.microsoft.com/vstudio/express/vwd/defa ult.aspx. This will allow you to mess around with the .NET framework and get a feel for the IDE - it is very similar to Visual Studio 2005. You will find lots of help on the forums at http://www.asp.net/ and this is a good starting point. The quickstart tutorials are great if you would like to wet your beak : http://www.asp.net/QUICKSTART/aspnet/Default.aspx.

  16. Re:WHY?? by XMyth · · Score: 2, Insightful

    Wow, you don't know how to setup your DB connection so it's .NET's fault? Do you really think it's an instability in the language that causes random security exceptions? Companies are running multi-million dollar systems using .NET technology (and MS SQL Server for the back-end..migrated FROM Oracle! ooooohhh) and you think it's got some kind of stupid random security exception error?

  17. I use .net by Oz0ne · · Score: 2, Insightful

    I like the .Net CLR alright, it serves my purposes well. Outside of large corporations I have yet to find a client who is interested in a java solution for anything. Most people's experience with java is limited to bad web pages, so the view is tainted. This carries through to most busineses. It's ignorance, yes. But honestly, how many people/companies that need an application know or care how it works--as long as it does the job?

  18. framework standardization by penguin-collective · · Score: 2, Insightful

    See, the thing is: these days, real-world programming skill is not about the language anymore, it's about the libraries. You may be able to switch from Java to C# in a few days, but knowing the libraries inside out is going to take a lot longer.

  19. Keep in mind that the writer of this by IAAP · · Score: 2, Insightful
    article is a freelancer with a BA English. The research probably was doing a search on Monster.com and seeing how many "jobs" cames up (we all know how that works) and then this person probably talked to their friend who's heard how much (complete guess) her .NET developer friend is making. That's about it. These folks make shit (this article probably got the authoer $200 at most) and they have to pump this crap out as fast as they can to just eat.

    These writers don't know anything.

  20. Re:Supply and demand by ThePyro · · Score: 2, Insightful
    Don't blame the guy you hired for your lack of investigation before hiring him.
    Don't blame the guy who flat-out lied to us? Yes, maybe we should have investigated him better, but it's ridiculous to say that none of the blame falls on him. It's exactly that kind of mindset which leads people to lying on their resumes in the first place. They have no appreciation for the damage they do by misrepresenting their capabilities, thinking that it's somebody else's responsibility to clean up their mess.

    We made a bad call, but that certainly doesn't let him off the hook.

  21. Re:Wow, wish I made that much... by jallen02 · · Score: 3, Insightful

    I get three weeks of vacation. Most folks do. God-Bothering.. bothers me too. GE food? Ehh.. we ship that stuff all over the world. Its hard to know exactly where your food came from.
     
    The shootings... I am not exactly sure what you mean by this. People do get shot yes.. but it is not like we all run around in fear of being shot. Statistically it is one of the least likely ways for you to die. Heart disease is much worse over here.
     
    I am no apologist, but please pick on us for stuff that is actually bad like our idiot politicians that are bankrupting the country and such.

    Jeremy

  22. QA is not testing, testing is not QA by metamatic · · Score: 4, Insightful

    Anyone who confuses unit testing with QA shouldn't be developing software.

    (Sorry, I'm not going to summarize a couple of decades of SWEng experience for Slashdot, just do more reading on the subject.)

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  23. And Tomorrow... by MightyMartian · · Score: 4, Insightful
    And tomorrow it will be something else. You know, I've been an amateur to semi-professional programmer for over twenty years now, and at least once every couple of years I've heard the same spiel about this language or that platform. Oooh, "language x" or "library y" is going to revolutionize the industry. Abandon all your C++ code, it's irrelevant and you'll be a starving artist if you don't immediately shift gears, etc. blah blah blah

    The real skill that a programmer needs if he or she is going to make it is adaptability. Stop thinking in terms of languages, period. At the core, unless you're having to do some pretty wild coding, most work pretty much the same. Think in terms of projects. If you're a freelancer, you'll want to have your finger in lots of pies, and if you're an in-house programmer, well, you know, the boss man is going to tell you what you're coding in. Flex the conceptual skills, because last week it was Delphi and VB, yesterday it was Java, today it's .Net, tomorrow it will be Ruby, and who the hell knows what next week will bring.

    Like it or not, the programmer is just as much a slave to consumerism as anyone else, though it comes from a different angle. Managers and customers are sold platforms and languages by marketing guys (you know, the kinds of guys that get these sorts of articles planted in CNN), and you're going to have to adapt. It's really sucky, but that's the nature of the game. It's not like the olden days where a guy could learn Cobol and have a job until he dropped dead into the card reader.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  24. It's getting hard to troll like that. by twitter · · Score: 2, Insightful
    Lilnobody presents a long flame of perl and claims no one would be hired to do perl work. With resources like the Wikipedia, such trolls are hard to pull off:

    It has been used since the early days of the Web to write CGI scripts, and is an integral component of the popular LAMP (Linux / Apache / MySQL / (Perl / PHP / Python)) platform for web development. Perl has been called "the glue that holds the web together". Large projects written in Perl include Slash, early implementations of PHP [1], and UseModWiki, the wiki software used in Wikipedia until 2002. ... New features have been added, yet virtually complete backwards compatibility with earlier versions is maintained.

    So, if Perl is good enough to manage Slashdot and Wiki, I imagine it's good enough to manage any "enterprise" site and is very much worth knowing.

    People are indeed hiring people who know perl. There might not be a spike in demand like there is in the non free world, where all the "partners" move lock step, but the jobs are there. I like the way Wall put it, "What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against?" Companies that don't mind spending lots of money will continue to persue .NET, C#, M$whatever, and crack lots of heads doing it.

    --

    Friends don't help friends install M$ junk.

  25. Re:Kill me...kill me please. by kurt_cagle · · Score: 2, Insightful

    >Furthermore, just because C/C++ is a "faster" language, that doesn't imply its better suited to web development, or even windows app development.

    However, nor would I say that the implied corrolary, that C# is better suited to web development work, is true. Overhead on C# work in the web development sphere is in fact actually driving a lot of companies who HAD gone to ASP.NET to switch over to *nix/Ruby or Python.

    Finally a general note - as someone authorized to hire programmers, I generally look for breadth of experience in a number of different languages and backgrounds. I KNOW that these people can learn .NET or Ruby quickly if they don't know it already, whereas I'm likely to be much more dubious about someone who claims.NET experience right out of college. Learn XML and a good declarative language (Haskell, Scheme or Ocaml perhaps), pick up some DECENT Javascript skills, a good strongly typed language like C# or Java, and dome background on work methodologies and design practices, and you'll be eminently more attractive to IT hiring managers.

  26. OOP != OOP by pijokela · · Score: 4, Insightful

    Ok. I learned OOP in my freshman year too. Then, after graduation and a couple years of experience I realized that I didn't know shit on my freshman year. OOP really is something that takes both experience and theory to be really powerful.

    In fact, I'd say the first two years after graduation I was a pretty crappy developer. I didn't know it of course, but later it has really hit me.

  27. Re:They don't know what .NET is by Randolpho · · Score: 3, Insightful

    Does anyone else see the problem with this? .Net is so platform specific that most of what you learn is non-portable.

    Nothing learned while programming is non-portable. The basic concepts of programming, as well as everything built on those concpts, are the same in any language.

    --
    "Times have not become more violent. They have just become more televised."
    -Marilyn Manson
  28. Re:I'm Job Searching by lip_spork · · Score: 3, Insightful

    .NET is not the skill you need to "break into IT". Nor is any other platform or language.

    It's my personal opinion is that the mentality a successful programming career requires is something you almost have to be born with. You need to not only excel at solving complex problems on your own, but must enjoy it. There are plenty of very smart people (smarter than me) who can't put together a simple app - they just don't have the patience.

    You're reading slashdot - that's a good sign. But I'd be suspicious of someone trying to enter the field who hadn't picked up some skills on their own, as a hobby. I bought my first computer in 8th grade (1983) and spent much of my high school years making games on it. I wrote an adventure game on my HP calculator. This may sound ridiculous but I'll bet a lot of people reading this have similar stories. Most of the programmers I know are basically introverted - not in any extreme way, they just function well on their own. Someone with a very outgoing personality, a "people person", would probably do better in another field. For someone who's intelligent and ambitious, there are plenty of jobs that pay better than programmer.

    That said, if you're confident that you should be a programmer, I'd say learning .NET on your own with books and tutorials would be a good first step. If it doesn't hold your interest then it probably wasn't meant to be.

    Unless you have a CS degree, your .NET noodling alone is not likely to land you a job. Fortunately for you there is a really low barrier to entry into the programming profession. I'll tell you what's worked for me and other people I know. Hire on to a small to medium sized company (if you're not in one already) with an IT infrastructure, but not a mature software development division. Start in whatever menial position you can qualify for, but let your abilities and interests be known to the IT group. Then look for opportunities - processes that you could help automate using MS Access, scripting, or whatever they have on hand. If you do well I guarantee you there will be no lack of projects coming your way, and in a couple of years you'll have some good resume fodder. This approach will gain you valuable industry insight and business analysis skills as well - something that university taught developers often lack. Hopefully your novice code and ill-conceived projects won't have too much damage before you can join a real development team, and learn about the software development lifecycle.

    Good Luck

  29. Re:I'd say thats about right by GlassHeart · · Score: 2, Insightful
    This is good for QA folk who eventually want to migrate into development, as they'll gain valuable skills along the way.

    The ideal QA person is one who actually enjoys breaking stuff, and will hone his or her skills at it for years to come. One who already wants to migrate to development can have the wrong frame of mind (as to what their job should be), as well as conflicts of interest (don't piss off the development manager). I say this as a developer who has great respect for good, professional QA people.

  30. C/C++ by Anonymous Coward · · Score: 1, Insightful

    For the "umpteenth" time, please don't be a wanker. C++ was conceived as "C with Classes" (i.e., an extension of C). Valid C code compiles under C++. There's quite a bit more than just "a relation between the two".

  31. My experience in NYC financial by Barcoder · · Score: 3, Insightful

    So, while this article says that demand is high for "Developers who are expert users of Microsoft's software programming language .NET...". You should focus on the key-word here, "expert". I think what they are infering here are people who know the ins-and-outs of the framework and the language, the software engineering process.

    We have high demand for "expert" .Net developers. But the pool is so limited. Most candidates we interview come from non-enterprise groups. Their knowledge of the framework (or any framework) is limited. And they lack sound software engineering experience.

    We do find plenty of Java developers with enterprise experience and from rich software engineering experience. We've hired Java developers for .Net positions, and in all cases they have transitioned well and exceeded expectations.

    So, for my company at least, we have high demand for "expert" .Net developers which is being met by java developers.

    My company's experience might be unique considering we are in NYC, and many of the Java folks we interview are from large financials.