Live data from Hacker News

CEO Friday: Why we don’t hire .NET programmers

blog.expensify.com

31–40 of 79 posts

Re: CEO Friday: Why we don’t hire .NET programmers

#31
I think this is just a rant by some CEO who hasn't had much real world experience. Sadly, it doesn't give any examples of why .NET is worse.

I would question why he REALLY doesn't like .NET. This article to me it like a person stuck inside a box with only peep hole towards the java stack. When he realizes that there is more to life and academics than just java or objective C, then maybe we will talk.

Can we please not keep up voting this rant that I didn't learn anything from except for the comments posted here on HN?

Re: CEO Friday: Why we don’t hire .NET programmers

#33
I honestly would never work for this guy. I have a C, Python, Java, Ruby background (as in what I've used in past jobs), and I'm working with .Net currently even though I'm a Ruby fan. I find C# and ASP MVC, pretty freaking good, even though I'm a Windows hater. Close minded people like this dude don't deserve good programming talent at all.

I might not be one of the best programers ever (I'm probably not!), but even if I was I'd send the same message to this guy: "I play almost every stringed instrument from the violin to the piano. I can juggle up to 5 objects with ease. I know a quite a few magic tricks. I'm freaking special and I will never work for a narrow minded person such as yourself. Even if you pay me a quadrillion nigerian dollars."

Re: CEO Friday: Why we don’t hire .NET programmers

#34
The Author of this article obviously has some misconceptions about .NET, and has probably had some bad experiences with enterprise developers. I've worked at two very successful startups that have used .NET for high traffic web development (and no, I'm not talking about MySpace). Some sites dealing with 5million + page views a day, and some of our .NET services would handle 5billion+ requests a month. It is great for large teams, the CLR is well optimized, and C# is a beautiful language in itself (although the platform supports many scripting and functional languages). I believe what the Author really means, is stay away from seasoned Asp.net web form developers who have never strayed from .NET and have no experience in an agile environment... if you are looking to hire for your startup. I've been hiring quite a few developers recently for the once startup I'm currently working at, and when recruiting I make sure to never start discriminating based on the language that an engineer develops in. I've hired programmers who were mainly developing in C++, Java, Python, PHP, and many other languages. If they are Jr, you just need to be super smart problem solver with decent programming skills. If you are Sr./Lead, you need high traffic experience, along with being well skilled with a strongly typed language, among other requirements. These kind of candidates have done extremely well, and enjoy the .NET platform that we mainly develop in. And me personally, I prefer .NET, but if the team and product is great, I would be happy to work with Ruby, Python, .NET, Java, etc... I think my PHP days are over though=)

Re: CEO Friday: Why we don’t hire .NET programmers

#36
I have a hard time taking this seriously beyond the ".NET is a language" statements. I don't think most of his statements really apply to C#, but they certainly don't apply to F#.

This is cargo cult management at its finest. The author is clearly one step above knowing absolutely nothing about this at all. It reads like he got burned by a bad hire and now everyone who shares traits in common with that person is also a bad hire.

Re: CEO Friday: Why we don’t hire .NET programmers

#37
post #3

This strikes me as the rantings of a CEO who doesn't have any touch with the reality of development. Thanks for the offer, but I wouldn't want to work for you anyway ;) In all seriousness, I just don't buy that .NET is an amateur language that prevents you from doing certain things. C# is a great, rapidly evolving language with a lot of functional programming features built in. On the other hand (as a developer who u…

A lot of .NET hate these last couple days. I consider myself a polyglot, but most of the work I do these days is in .NET. I agree, there's no limitation on what you can do with the languages -- its the frameworks that limit you. Isn't that true with Rails, Django, Struts, and just about any other framework?

As far as languages being a red flag on resumes? I'd argue the more you see, the better. You don't want to see 30 years of C/C++ and nothing else, nor do you want to see someone with 1 year of each language. You want to see passion, dedication, and a genuine desire to learn.

I think the real issue is how much you can make as a .NET developer. Enterprise clients buy things that come in boxes. Rails doesn't come in a box, and it doesn't come with a support contract or a lifecycle agreement. There's something to be said for easy migration from version to version, tested hotfixes, and a fully integrated stack from app code to db server.

Anyways,

Re: CEO Friday: Why we don’t hire .NET programmers

#38
I wish the author of this piece the very best with his squirrel restaurant franchise.

Seriously, what the hell is this guy going on about? The fact that large companies that create huge ecosystems also create cookie-cutter ways of doing things? And this is bad?

I've coded in just about everything out there except Haskell and Lisp. I've worked with heavy web-centric systems, distributed systems, P2P systems, and so on. I've written drivers, shell extensions, and rules-based database applications. And yes, it's true, I'm moving more to linux and F# on mono lately. But that's because of licensing and scaling issues, not because the .NET stack is somehow defective. In fact, if .NET were a liability, I would very quickly jump into something else. But it's not.

It's also true that there are a LOT of .NET developers who understand the cookie-cutter approach and can't go outside a very small comfort zone. But that's a product of being the world-wide standard, not a product of something gone wrong. When you own the game, hundreds of thousands of folks are going to go through 6-week "learn .NET!" courses and come out the other end button-pushers. If anything, those guys are a sign of a mature market, which is a good thing.

And what's this about .NET being a language? He acts like this entire system is similar to what? Javascript? .NET is a platform which runs dozens of languages with hundreds of thousands of easily pluggable libraries. If you're coding C++ in .NET writing unmanaged code you're doing something completely different from some guy dragging and dropping controls on a web page in VB.NET

This article shows the worst thing about all of us as programmers: we tend to run on assuming that we are experts in areas where we have the slimmest idea of what the hell we are actually talking about.

In fact, I feel this article is so bad that it has to be a joke: a poke with a sharp stick just to incite a lot of invective comments, like this one. Fricking linkbait. Bah.

Re: CEO Friday: Why we don’t hire .NET programmers

#39
I'm going to keep my response brief: 1) .NET is not a language, and calling it such is just silly. 2) I've built everything from insanely high-performance emulators (IronBabel) to kernels (Renraku) to computer vision applications (not announced yet) using .NET; all of these are "1.7oz burgers", and all of them were performant, flexible, and easy to build.

Troll, troll, troll...

Re: CEO Friday: Why we don’t hire .NET programmers

#40
First of all, what flamebait but I'll bite

"Even worse, every day spent learning a Microsoft kitchen takes TWO days to unlearn, meaning once you get a reasonable way down the .NET career path, there is almost no going back."

That's not true in my experience.

I work at small, profitable company using Linux / Python / Amazon Web Services, we have some fantastic developers who came from a pure .NET background - some worked at Microsoft.

They transitioned successfully because of their attitude. If you commit yourself to learning the tools and not fighting them, you can make the transition in a couple months - no problem.

Post reply on HN