Ask HN: Am I doing wrong?

You have 8 years of Microsoft development experience that's pretty decent and I bet this will bring you a lot of good jobs because many companies are using Microsoft technologies even the crappy ones (VB.Net, Classic VB).<p>However you are absolutely right about Microsoft. Yeah they doing good lately but from which standpoint? Microsoft has a really bad reputation under hackers and I think the reason is not that we all love Apple and Mac's. No, I think those reasons become clear if you look at what Microsoft is doing all the time, what are they implementing, how are they implementing new technologies.<p>For example Internet Explorer 9. This time Microsoft has to be really good cause they are losing market share month after month. And luckily Microsoft did understand that and they are doing good with Internet Explorer 9 but again they are making things their own way and that's what is bad about them. If Microsoft thinks it needs something they are always developing it on their own without looking what other developers are doing and how they solved those problems. No, they have always this one Microsoft solution doesn't play really good with the rest of the world (and sometimes even with Microsoft software). That's Microsoft.<p>However I think you are on the wrong way. If your profession is Microsoft technologies and you want to stick with that cause you have a job and you like Microsoft platforms then you should stick with it and become better and better.<p>But look what other developers and hackers are doing, which new thinks are coming, which things are slowly going and compared to that what is Microsoft doing. Don't turn into a developer who has a Microsoft hammer in his hands that's the worst thing you can do for the world and for your career.<p>I hope I could help you.<p>BTW: I learned programming with C#

Welcome to the fire&#38;motion effect[1]. You now have three problems.<p>First, by chasing what some <i>other</i> people think is sexy technology, as opposed to going with what allows you do Get The Job Done, and quick.<p>Second, your misunderstanding on what the markets care (which is, well, marketing for the most part), and don't care about (eg your technological stack). None of these the things outlined in your post will make any difference whatsoever on your ability to chase lucrative market opportunities.<p>Third. Despite what some people here might write, "Hacking" -fiddling with technologies, and gaining a deep insight into them- is completely technological agnostics. You can be a hacker, even in VB.NET; it just happens, that some of these technologies has a better "average community member insight" factor, than others.<p>Thus, your question really boils down to something more fundamental: are you into "hacking" for the tech, or for the people? In the former case, it doesn't really matter whether you'll use MS, or Python, or what the state of the current MS devtools are -just that you gain a deep understanding of them.<p>In the later case, you should put your investment into <i>people</i> -the ones you'd want to connect with, anyway- and let the appropriate tech emerge from it naturally.<p>[1] <a href="http://www.joelonsoftware.com/articles/fog0000000339.html" rel="nofollow">http://www.joelonsoftware.com/articles/fog0000000339.html</a>

Worrying about the development language you use is like worrying about using a Stanley hammer versus a Craftsman hammer when building a house. The brand doesn't matter as long as the house gets built.<p>I've worked in the .NET stack for about 5 years now. It is a real pleasure to work with. When I need to get something done, I know I can do it easily, and without problems. And seeing the recent developments of Java with Oracle, I feel my decision was that much better.

There's nothing inherently wrong with knowing Microsoft technology well. It's a tool. Learning more languages is a great goal because you can learn to use different types of tools. This gives you the ability to choose which tool is right for the job you're working on, instead of being limited to the one you know well.<p>My first experience was in VB and then C#, and I love ASP.NET MVC and still use it for some projects where it makes sense. But having learned other languages I've learned what the limitations of that technology is, and for most things I work on nowadays Microsoft technology is not the best solution.<p>Depending on what you spend time learning and what types of problems you work on, you may come up with different conclusions, and that's totally valid.

The lack of MSFT traction with startups has more to do with cost than cool. (Biz Spark is temporary - they get you in the end).<p>At my last startup job we used the microsoft stack very effectively - the cofounder was a microsoft guy, so that's what we used. Not a big deal.

I call BS. A "Hacker" is not bound by a technology or language, despite what the [insert language or technology here] bigots want you to think. If you can create a spaceship from a toaster, who cares if it uses nanotechnology? It's still cool.<p>Go on working in whatever language or technology you want, and don't listen to the idiot zealots who aren't intelligent enough to broaden their horizons to the point where they understand that ANY language is cool if it provides the customers with a viable solution that scales.<p>Cheers.

I think it depends on your goals. Some ideas:<p>If you want to work for a startup then you'd probably need to learn open source tools (though startups use the MS stack, too). You might also find that a detour into OSS helps you bring fresh ideas back to your MS work.<p>If you need a job and/or like working with MS stuff, then stick with that (and be shamed on HN ;).<p>If you want to build a product, then it doesn't really matter--it's more important to bring something successfully to market.

When most people claim that language X is "not cool" it's a defense mechanism. They do not know or have no interest in learning X, so it becomes worthless and uncool to them.<p>Spend more time focusing on theory and less on stack.<p>As for stack advice, pick what you want to do.

Do both.<p>Nothing wrong with cross training. Athletes cross train to help them perform better in their chosen speciality, so should programmers.<p>I like to dabble in other languages and frameworks - my bread and butter comes from MS, but if I write a little util to automate something for myself at work or do a little side project, I use something different - it helps keep me interested and it helps round out my craft. I don't think losing a little traction on the most up to date MS tech will affect you as much as you think because you will probably be able to transfer your skills and approaches from other environments back to the MS equivalent pretty quickly. If you really are worried, take a few minutes every day <i>at work</i> to bone up on some MS stuff instead of reading that extra HN second page link to a blog post on "the 15 essential things you must do to become super successful" and all the related HN comments :).<p>On the "cool" aspect - cool is irrelevant if your work is satisfying.

Do whatever will make your stuff work. There are lots of reasons to dislike Microsoft, and plenty of reasons why the culture does not fit. That said, your users do not care how you've created their software, they want things that solve their problems.<p>Note that many of the articles here are totally stack agnostic, too.

Learn new stuff is given as the most constant is change itself.<p>Solve problems with what you are most effective with.<p>Have fun, use the lang/os/lib/whutnut make you smile while doing it. :-)<p>Apply above 3 points and hack! (Repeat as needed.)

A question you may have to answer yourself might be:<p>1) Are you looking to have a safe job type career?<p>or<p>2) Are you trying to build something that you have in mind?