[mobiuscog]

I would suggest that good .NET developers (like any other language, etc.) are the ones that aren't constantly looking for a 'new technology' to move into, and instead get on with writing quality software / solving the problem at hand.

[tracker1]

I'm not sure I entirely agree with that. A lot of times, people get stuck on a certain tooling, or patterns even when they don't apply. In particular with .Net, is the Data Application Blocks of Enterprise Library, and the rest of entlib in general.

Most of which only makes software more complicated than usually necessary, and makes me shudder to this day when I hear the term "Enterprise" applied to software. It isn't that it doesn't work, or that it never serves a purpose, but that most of the time it is applied it isn't good.

I spent the better part of the 2000's writing code in C#, it's still a favorite language. I've spend most of the past 5-6 years writing far more JS, and a lot of Node migration. Some of that isn't so great either. In the end, writing code that's easy to setup, configure, follow and understand is more important than any language specifics, and I feel that Java and C# developers forget that in favor of "Enterprise" practices.

[lujim]

I think that it's also common for teams to get painted into a corner trying to use the next great, bleeding edge, thing. I too shudder at the term "Enterprise", but I also shudder when I see a company desperately trying to hire a "NoSQL Expert" at any cost because they built everything around Mongo when a relational database would have been fine.

[tracker1]

True enough, though I actually like mongo's document centric database for a lot of use cases. Though with MS-SQL 2016, Postgres + plv8 and binary-json, and rethinkdb, there are better options these days.