State of .Net Market

[escapeUK]

Yep I'd agree with that.
VB.NET code generally looks like this:
Too long methods
Too big classes
Poor OO concepts
Too great a reliance on CONSTANTS
Too many parameters in method signatures
In a nutshell : not SOLID code.

Compared to what? And if a method needs a lot of parameters to work, what is this mythical language that lets you pass fewer? You can define scope on variables in vb you know.

[xing]

Compared to what? And if a method needs a lot of parameters to work, what is this mythical language that lets you pass fewer? You can define scope on variables in vb you know.

If a method needs a lot of parameters, it means either it has too many responsibilities (the method should be broken down into several methods) or all the parameters together represent a single concept (all the parameters should be put into a class).

Just no one actually bothers to make things right.

[oliverson]

Not sure what you're talking about methods and parameters.

All my C# code takes place in one method called Main()

No wonder I can't get a contract eh?

:-D

[Scoobos]

I'd say that rather than bash the language, the problems are more in how easy it is to produce rubbish code now.

In 1998 we were using 450Mhz PIII cpus with less than 256mb of ram in desktops, and VB just wasnt viable for number crunching, I think the exponential rise in hardware has resulted in the production of worse quality software.

I wish I had time to properly study the whole situation, but in my first bosses opinion (he worked for IBM since 1950) he saw any language other than machine code to be inefficient.

Its great that we've got all these libraries to include and use, but I think it detracts from people learning how to code well in the first place. I think the majority (huge software corporations included) are getting away with producing really inefficient , crappy code - because we aren't seeing a huge impact on thread execution times.

[russell]

I'd say that rather than bash the language, the problems are more in how easy it is to produce rubbish code now.

In 1998 we were using 450Mhz PIII cpus with less than 256mb of ram in desktops, and VB just wasnt viable for number crunching, I think the exponential rise in hardware has resulted in the production of worse quality software.

I wish I had time to properly study the whole situation, but in my first bosses opinion (he worked for IBM since 1950) he saw any language other than machine code to be inefficient.

Its great that we've got all these libraries to include and use, but I think it detracts from people learning how to code well in the first place. I think the majority (huge software corporations included) are getting away with producing really inefficient , crappy code - because we aren't seeing a huge impact on thread execution times.

This is very true, and the old "Premature Optimization is Evil" is usually dragged out as a counter. However when you write a pile of over engineered tulip on top of a pile of junk framework (think ASP.NET) to simply server a web page, then maybe Optimization should be at least considered earlier.

[wonderboy]

As a .NET contractor currently looking I have to agree that the market is dire.

My personal opinion is that the economy is basically broken and even growth sectors like tech are feeling the pinch ...hence no new big projects / urgent development work, hence very few contracts.

My (admittedly cynical) prediction is that this will go on for some time unfortunately...

Best of luck to us all!

[escapeUK]

As a .NET contractor currently looking I have to agree that the market is dire.

What do you do specifically? I dont work via agencies (well I haven't so far), but through my network of contacts. None of my contacts probably have any idea what .NET is, just that I solve computer problems and make lovely programs. There is a bit of a queue for my talents, and I dont think I do anything you probably cant. I just understand what the businesses problems are, suggest how things might be automated and then deliver what I suggested.

[wonderboy]

What do you do specifically?

C#, ASP.NET MVC 3, JavaScript. Like yourself, I avoid using agents and I have found it incredibly difficult to get any traction with companies (and I have contacted a large number - mostly by emailing them my CV with a covering note).

Now, possibly I should put some more effort in and telephone more of them (I telephone the odd one) to avoid the careers@foo.com blackhole.

Small-ish companies (and sometimes even what I would call mid-sized; 100-500 person companies) seem to strongly prefer permies, and large companies typically have a massive barrier of preferred suppliers, HR and god-awful "taleo" recruitment pages in the way of direct contact.

Finally, I aim for the top end of the rate range for the roles I apply for, and this may hinder my cause somewhat (this doesn't account for the general lack of interest before the rate is disclosed though).

I've only being doing this game for a couple of years and so I am open to advice.

[escapeUK]

I would be surprised if sending CVs in blindly would work. Chances are it isnt going to the right person, and even if it did the chances of them knowing what all the fancy sounding things on your CV meant are slim to none. What they actually need to know is that you can solve their problems, unfortunately you dont know what their problems are, they might not even know themselves.

I seemed to have worked with a few people who have gone onto bigger and better things, and who remember me. And when an IT problem comes up, they think that I could help. Some people use Linkedin to keep in touch, I never have, but an odd e-mail every few months (not when I want something, just generally) is all it takes. Often mentioning the project Im currently working on (in very generic terms) often gets a response of "We need something like that here!" Its not a .NET program, creating records in a SQL database from an estimating spreadsheet. Its a way to create sales orders instantly.

If I didnt have the contacts, I wouldnt rule out agents.

[wonderboy]

Hey thanks for the response, sounds like pragmatic advice.

Of course, I am not sending my CV completely "blindly". I am finding companies who use the correct stack who either have an advertised need for someone with my skills (may be permanent, but I put in the speculative application anyway), or large enough for me to suspect that they will likely need someone either now or in the short term.

I use LinkedIn heavily for researching my "targets".

I suspect you are right about my communiques frequently not going to the right person though...