Stick with one technology or go for several technologies?


When starting a small software business what would be ideal and why? I mean in the context of technologies

1- Stick with only one technology ( ex: only Java )

2- Go for several technologies ( Java , .NET ....)

if answer is no1 , how to decide a suitable technology.

Getting Started Software Decision Small Business

asked Oct 13 '11 at 13:40
D Shan
68 points
Get up to $750K in working capital to finance your business: Clarify Capital Business Loans
  • why does technology matter at all? Shouldn't the focus be solving a problem for customers? Pick one technology that does the job - some issues would be - accessibility for getting good people, your own experience and productivity – Tim J 12 years ago
  • Of course.As far as I understand picking one technology would be better in longterm as the company will become an expert in a particular scope.What I wonder is whether it'll be a matter when sustainability is concerned. – D Shan 12 years ago

2 Answers


Think sensible. M;ultiple technologies are multiple times the need of knowledge (sorry, good people specialize - yes, I do know java,from 10 years ago, but I do .NET ever since) and infrastructure (build servers etc.) AND time (yes, they may be similar, but there still is overhead - every bug must be fixed multiple times and tested etc.

A small vertical stack is superior from that. Once you hit a good income side you may decide it is worth pursuing multiple techs at the same time, but not at the beginning.

That said - I see .NET superior to java IF you can live with the mostly Microsoft only / Windows only environment (which still accustoms for 90% or more of the desktops - seres dont matter because every larger shop can host a .NET server). Why? It has a higher more widely used stack, which makes it easier to deal with it.

Costs are a non-issue - MS has great programs for the first years of startups. And later, sorry, the cost of a MSDN license per developer are small compared to a decent salary anyway.

This is 100% NOT a technology decision - it is an economic one. Every cost you put up has to have a justification, especially in a startup phase. I personally would try to build a stack where I dont have to hire multiple people to do what otherwise less people can be good at.

answered Oct 13 '11 at 15:05
Net Tecture
11 points


Basically I think you should become really good with one first ... then consider taking on new technologies otherwise you won't get anywhere deep with any of them.

As for which one to choose? Well thats much harder,

  • What is your intended market? As a startup its usually, anyone who will pay me. 14 years ago we started using VB6 because all the work we could find was in VB6 and MS Access. This is a key factor when your looking.
  • What is supported? Both but when there is a problem I know the .NET documentation is pretty hard to beat ... that said Stackoverflow covers most of your issues here.
  • Who can you hire around your local area? As you grow this will become more important, if you pick JAVA and your local community is more .NET focused then your in trouble.
  • Does it have a good community around it? I'm into the .NET one and can't really speak for the JAVA one, its probably as good though seems a little more "we are better than you " ... but then i'm biased :)
  • Does it have a large amount of 3rd party components? This is important for getting the job done fast, spend $100 to save 2 days work will be a viable option at some point.

Both JAVA and .NET, in general tick all the boxes, so it comes down to, what do you enjoy working on more? because its your life for the next X years you better like the language, the development environemnt, the community and everything else that goes with the choice.

answered Oct 13 '11 at 15:43
Robin Vessey
8,394 points

Your Answer

  • Bold
  • Italic
  • • Bullets
  • 1. Numbers
  • Quote
Not the answer you're looking for? Ask your own question or browse other questions in these topics:

Getting Started Software Decision Small Business