Sitemap
Varun Vohra

Varun Vohra

I write about Business, Strategy, Product and Technology. All things startups. Based in Bangalore. Views expressed are solely my own.

Thinking through your technology choices.

6 min readMay 27, 2016

--

Press enter or click to view image in full size
Decision trees can be oh so beautiful. Alas, not always helpful!

Over the past several years, I've built and launched multiple software products for a number of clients. Many of them were consumer facing web applications, while a few were business tools meant for internal use. All of them were on the cloud, no exceptions. Between them I've used many different technologies and 4 core languages, namely Ruby, PHP, C# and JavaScript. Do you know what each and every one of these products had in common? The people behind the products (entrepreneurs, CXOs, small business owners, product heads), all asked me this question:

What technology should we use for this new product we're building?

No one has ever failed to ask me this question, that too with the tone of utmost importance. Even when there is a technologist behind the idea, with a pre-existing belief that this question has a right answer (which they know), they still ask. After years of repetition, it has just become annoying. Do you know another thing that each and every one of the products I've built had in common?

Not one of their customers gave a damn about the technology that was used.
Not one.

Nowadays, when people ask me what technologies they should use for their product, I just don't know how to answer. Truth be told, while customers don't care about your technology choices, those choices do matter for your project or startup.

Don't let it matter for the wrong reasons.

Whenever I've had a conversation on technology stacks, the reasons why people believe it matters seem legit. It’s amazing (and I'm thankful) that no one has actually said to me that their end users will care about it. However, the concerns that arise when discussing technology choices tend to fall squarely into a few popular categories.

Viability: Can this be done using this technology?

The answer is almost always ‘Yes’. A good idea, especially in the world of web and cloud based applications, can be built using almost any technology. In the past 3 years, only one exception comes to mind. I had to build a cryptographic algorithm validation tool that needed to work in kernel space for which the only real choice was using C. Now if that’s the kind of product or app you're looking to build, there might be some limitations, if not — the world is your oyster.

Scalability: Will this technology be able to handle a 100 million users?

This is a genuine concern that many founders / project owners have. The internet is filled examples of products that started out well and failed to reach critical mass because of constant outages and technical failures. What they probably don't know is that engineering quality, infrastructure and application architecture determine scalability and reliability far more than the underlying technology used to build the product.

Reliability: Have other successful products been built using this tech?

Every technology has pros and cons which you will have to make your peace with. Some offer speed of development while others offer more robust testing frameworks. From everything I know right now, there is no proven correlation between the technology used and the success of a project / startup.

There is only one real reason why your technology stack is important — different technologies have different engineering cultures.

Get Varun Vohra’s stories in your inbox

Join Medium for free to get updates from this writer.

Good engineers care about the technology they use. Their views on workflows, relevance of testing/spec writing/documentation/community contributions all get strongly influenced by the technology they use. For example, engineers that work primarily in .NET technologies will typically not value open source software the same way that engineers that use Node.js would.

In the end, the technology you choose impacts your team’s culture. Like all team building and culture creation, this is an upfront decision that has long term effect since it’s difficult to change. If you have a CTO or technical cofounder, go with the technology that he or she is most comfortable with. If you don't have a technical partner helping you make this decision, try using relevant business metrics to make one.

Personally, I love the MEAN and Ruby on Rails tech stacks and the engineering cultures associated with them. If you want to know more about why, you can check out these 9 short videos on youtube ☺

Making an informed decision isn't easy.

If you're reading past this point, I'll assume that you (and your partners / team) don't have a technology background. If you have an existing team, please don’t worry about choosing a technology — just roll with whatever they are happy and comfortable with. Focus instead on things that will affect the success of your product or venture. When you're just starting out and there is no existing team in place, there are four key factors you can look at to help you decide.

Community

The size of the community for a particular technology plays an important role in determining how many ready-to-use libraries, components, integrations are readily available online for your team to use. Even more significantly, it impacts the speed with which your team will be able to overcome technical hurdles — all engineers help their fellow engineers (it’s like the bro code). An easy way to discover the size of the community is to visit stackoverflow.com and check how many users follow a particular technology.

Press enter or click to view image in full size
some of the most popular technology ‘tags’ on stackoverflow

Hiring

Finding good talent is always a challenge and you don't want your technology choices to further increase the difficulty of assembling a great team. Having said that, if you choose a cutting edge technology, you might be able to attract some very talented engineers since they won't get many opportunities to work in those technologies in other organizations. One of the simplest ways to discover the size of the talent pool for a technology is to search for it on popular job boards. Keep in mind that you need to search within geographic constraints since concentrations of technology specializations are not the same everywhere.

Press enter or click to view image in full size
naukri.com results for nodejs devs in mumbai

Costs

Like with any marketplace, the economics of supply and demand are always at play in the job market. So when you find fewer people with a certain skill, it’s almost certain that they will come at higher price points. The nice thing about this is that they tend to be better engineers since technologies that aren't extremely popular are usually self-taught and not the first language that they learn. The other factor of cost is license fees. Proprietary technologies such as .NET or Oracle, even Windows, come with costs attached to their commercial use. These license fees may seem affordable in the early stages, but as your business scales they can really hurt, even more so when you meet a competitor that mentions his/her open source stack costing nothing at all.

Time to market

While always an important consideration, time to market becomes even more important if you're a startup or an early mover in an industry. Certain technologies have frameworks and functionalities that enable them to build web apps faster than others. Other aspects might suffer in such choices, but as I've already mentioned, any choice you make comes with a business trade-off. For example, Ruby on Rails as a framework makes rapid prototyping easier for web applications while some Java based frameworks make it a more time consuming process.

Technology choices matter, but they aren't critical to your success. I hope after reading this you decide to spend a limited amount of time on making this choice and focus your efforts on defining your MVP, marketing your product or raising the capital you'll need to sustain yourself till you make it big. Be clear on the engineering culture you want and the right technology will find you.

Lastly, remember that statistically picking a technology is like marriage, there’s more than a 50–50 chance you'll find someone younger and sexier before the decade’s up.

--

--

Varun Vohra
Varun Vohra

Written by Varun Vohra

I write about Business, Strategy, Product and Technology. All things startups. Based in Bangalore. Views expressed are solely my own.