Hacker News Reader

Comment by mrweasel | Hacker News Reader

I think that depends on where you live really. In the area I'm in being a .NET developer is clearly an advantage.

One reason I, and others like me have looked down on .NET developers, is that a large number of them aren't any good. I've meet brilliant .NET developer, some of the most talented developers I know are .NET developers, but the crappiest developers I know are .NET developers as well.

Some developers are completely ignorant in respect to computers, the Internet, algorithms and new technology in general, and they are almost exclusively working on Windows and by extension .NET. These are developers that can make code work, but take Visual Studio away from them and they cease to be developers.

It's by no means fair, because as I said, some of the best developers I know are .NET developers. It's just that I've never see anyone working on Linux/Unix be completely ignorant other languages, tools and platforms.

View on HN

Replace .NET with Java and Visual Studio with IDEA/Eclipse and you'd probably be right again with the same post. It's not really a .NET problem, more like a bell curve and popularity problem.

> These are developers that can make code work, but take Visual Studio away from them and they cease to be developers.

Ha, during my brief stint at a windows-shop after graduating, I did meet a few who couldn't get their heads around the concept of having a build happen without someone clicking a green triangle button in VS.

Considering the .NET stack has a heavy bias towards CI, that's hard to believe.

It probably varies by geography, but the .Net scene I was in really didn't have a bias toward CI at all (or testing, or almost any decent development practices).

I wont argue about it, our experiences differ, and that's cool :)

You'd be surprised. There's a lot of shops out there who have never heard of CI/CD/Automated Tests/etc.

There is nothing inherent about the .Net stack that makes it biased or preferential-towards CI. Other than the fact that you can "do it" in a CI context, I can't think of anything else. Care to enlighten me?

Bear in mind, a lot of .Net developers don't even know it's possible to compile their projects outside of Visual Studio. Msbuild, Nant, csc.exe, "what are those?"

The standard for .NET shops is TFS. When you create a TFS project you setup CI and automated builds.

"Bear in mind, a lot of .Net developers don't even know it's possible to compile their projects outside of Visual Studio. Msbuild, Nant, csc.exe, "what are those?" There's probably plenty of java developers like that as well.

>The standard for .NET shops is TFS

I've never seen Team Foundation Server in a .NET shop. It's either been SVN, Git or Perforce. That being said I think it's very individual, but many small companies won't pay for TFS, they barely want to pay for Visual Studio Professional/Enterprise edition

I've worked at a large financial company (everyone would recognize the name) and TFS was the main build system.

Those sorts of developers exist on every platform. The trendy platforms are simply too new for non-adaptable developers to have yet made themselves visible.

As someone who has done some stuff in Mono this is funny

Reply on news.ycombinator.com