Another head hunter who'll not get my head
-
Is it too early to post another of these? It's such a good example of the art. " Job Description:- We are looking for Senior DOT.NET Developer for one of our client in CA who should have with solid 7 - 10 years of DOT.NET Framework and WinForms development experience with WCF, WF, Microsoft Enterprise application blocks and Smart Client technologies. " What is this DOT.NET of which you speak? Your client should have seven to ten years experience? And remind me again... how long ago was .net 1.0 released? Wasn't it only six years ago? (2002-01-05 according to Wikipedia) I thought by now employers would have stopped suggesting that candidates should have been using .net since the betas. I read the C# spec way back in 1999 when the compiler was vaporware, does that count?
PIEBALDconsult wrote:
And remind me again... how long ago was .net 1.0 released? Wasn't it only six years ago? (2002-01-05 according to Wikipedia)
You have it right. When I was working for a large nameless retailer who must remain nameless but whose intials are TJX, we started working with .NET in June 06 and became early adopters of 2003 starting in Sptemeber of 2002. When POC was finished and the team was being upsized in the spring of 2003, HR started looking for programmers with "a minimum of four years of .NET experience in a production environment." That was bad enough. But then we got some applicants who claimed they had it. . . .
Jon Smith & Wesson: The original point and click interface
-
Is it too early to post another of these? It's such a good example of the art. " Job Description:- We are looking for Senior DOT.NET Developer for one of our client in CA who should have with solid 7 - 10 years of DOT.NET Framework and WinForms development experience with WCF, WF, Microsoft Enterprise application blocks and Smart Client technologies. " What is this DOT.NET of which you speak? Your client should have seven to ten years experience? And remind me again... how long ago was .net 1.0 released? Wasn't it only six years ago? (2002-01-05 according to Wikipedia) I thought by now employers would have stopped suggesting that candidates should have been using .net since the betas. I read the C# spec way back in 1999 when the compiler was vaporware, does that count?
I got my hands on an alpha version back in Dec of '00. It had the uncanny tendency of BSODing my machine while trying to display intellisense.
I'm largely language agnostic
After a while they all bug me :doh:
-
Is it too early to post another of these? It's such a good example of the art. " Job Description:- We are looking for Senior DOT.NET Developer for one of our client in CA who should have with solid 7 - 10 years of DOT.NET Framework and WinForms development experience with WCF, WF, Microsoft Enterprise application blocks and Smart Client technologies. " What is this DOT.NET of which you speak? Your client should have seven to ten years experience? And remind me again... how long ago was .net 1.0 released? Wasn't it only six years ago? (2002-01-05 according to Wikipedia) I thought by now employers would have stopped suggesting that candidates should have been using .net since the betas. I read the C# spec way back in 1999 when the compiler was vaporware, does that count?
-
The consultant is a tool (and therefore fully qualified for the role) but that doesnt mean that the job is not worth looking into.
Well no, but if the company hired him... Anyway, it's a six month contract four hundred miles away. We moved here from southern California. The email does say I can forward it... interested?
-
Well no, but if the company hired him... Anyway, it's a six month contract four hundred miles away. We moved here from southern California. The email does say I can forward it... interested?
PIEBALDconsult wrote:
Well no, but if the company hired him...
As an employer its just as hard to find a decent consultant as it is as a perspective employee
PIEBALDconsult wrote:
Anyway, it's a six month contract four hundred miles away. We moved here from southern California. The email does say I can forward it... interested?
It'd be a few 1000 miles for me so no but thanks :)
-
I got my hands on an alpha version back in Dec of '00. It had the uncanny tendency of BSODing my machine while trying to display intellisense.
I'm largely language agnostic
After a while they all bug me :doh:
I got in on the first beta. I remember reading a screaming fit in one of the forums set up to discuss this brand new programming environment, wherein a wise and thoughtful man complained because he'd installed the beta on his (only and therefore) production machine, and it broke MSWORD six ways from Sunday.
Jon Smith & Wesson: The original point and click interface
-
Well no, but if the company hired him... Anyway, it's a six month contract four hundred miles away. We moved here from southern California. The email does say I can forward it... interested?
PIEBALDconsult wrote:
Anyway, it's a six month contract four hundred miles away. We moved here from southern California.
I live in the Solomon Islands - An all expenses paid trip to somewhere that's not a "least developed country" would be nice for a break. Although I think I'd want to be paid in Euro's or Aussie Dollars considering the way the USD is tanking, and I'm guessing will continue to do so for some time yet.
-
Is it too early to post another of these? It's such a good example of the art. " Job Description:- We are looking for Senior DOT.NET Developer for one of our client in CA who should have with solid 7 - 10 years of DOT.NET Framework and WinForms development experience with WCF, WF, Microsoft Enterprise application blocks and Smart Client technologies. " What is this DOT.NET of which you speak? Your client should have seven to ten years experience? And remind me again... how long ago was .net 1.0 released? Wasn't it only six years ago? (2002-01-05 according to Wikipedia) I thought by now employers would have stopped suggesting that candidates should have been using .net since the betas. I read the C# spec way back in 1999 when the compiler was vaporware, does that count?
Technically mere mortals could have been playing with beta 1 of .NET 1.0 in June 2000, so you could have nearly 8 years experience, but the first year of that would be one of frustration
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Technically mere mortals could have been playing with beta 1 of .NET 1.0 in June 2000, so you could have nearly 8 years experience, but the first year of that would be one of frustration
cheers, Chris Maunder
CodeProject.com : C++ MVP
It was indeed. The only samples I could find were in VB.NET; and this strange Garbage Collector - what was that language you spoke of stranger?
Deja View - the feeling that you've seen this post before.
-
Is it too early to post another of these? It's such a good example of the art. " Job Description:- We are looking for Senior DOT.NET Developer for one of our client in CA who should have with solid 7 - 10 years of DOT.NET Framework and WinForms development experience with WCF, WF, Microsoft Enterprise application blocks and Smart Client technologies. " What is this DOT.NET of which you speak? Your client should have seven to ten years experience? And remind me again... how long ago was .net 1.0 released? Wasn't it only six years ago? (2002-01-05 according to Wikipedia) I thought by now employers would have stopped suggesting that candidates should have been using .net since the betas. I read the C# spec way back in 1999 when the compiler was vaporware, does that count?