Skip to main content

Biggest learning after 10 years of programming




Things will go wrong.

When I was younger, I tried all the new things. Whenever a new programming language came, or a new library/API was realized, I would be the first to try it out. It almost always made sense as these new things were being released to solve some problems and I would adapt them to solve my problems.

At first, they always work.

But then they start showing signs of problems. First small things, then big things and finally showstoppers and I would move back to tried and tested systems.

I see that trend a lot now. And we have very cool toys to play with. Redis, Mongo, Meteor, Firebase, Angular, nodejs etc.

Each new thing is good and I still play with all of them and I still use them in our products. But now, I always plan backups.

'cause I know that they will fail and thats why I program backups in case the new tools fail. I always fall back to the tried and tested. Also, for all our products, the foundation is still tried and tested tools like MySQL, Java, PHP and Apache.

Popular posts from this blog

Integrating Arborjs with Angular to create a live calls dashboard

Arborjs  is a cool graph visualization library. Angular  is one of the best JavaScript frameworks and we have been using Angular in a lot of our front end development. When you handle millions of calls, proper visualization becomes very important. Without proper visualization, you can get lost in the mountains of data. So we spend a lot of time to come up with good visualizations to represent the data. Since we loved the cool way in which Arbor represented graph data, we could not wait to hook it up with Angular. Because of Angular's two way data binding, when you hook up Angularjs with Arbor.js you can get a dynamically updated visualization of graph data with cool animations. To give back to the community, we have put up the code online at Github . Basically we have created an Angularjs directive for Arborjs. Please feel free to fork the code and add extensions and use it for your own visualizations. The code is self explanatory with comments inline. Best way to ...

First Post

In this blog, I will be talking about my experiences in trying to build a cloud telephony platform , KooKoo . Along the way I will also be talking about different design choices I made, good programming practices and the IVR domain in general. For technoratti: NNFJW8EW86C3

Cloud Telephony-History and state of the art

Well, its been 11 years since Twilio launched their voice API in November 2008. I would say that was a major turning point in the cloud telephony industry. Before that, for people to build telephony applications, you either had to depend on proprietary platforms like Avaya dialog designer or build on arcane technologies like VXML which again was supported at varying degrees by the incumbents. Enter Twilio with their voice API and the industry changed for the better. Since it's been almost 11 years now I thought now might be a good time to do a comprehensive review of the cloud telephony industry as a whole in general and in India in particular. The Beginning Twilio was undoubtedly the startup which ushered in the era of cloud telephony. They started in November 2008. At that time in India, we at Ozonetel had launched a hosted VXML platform. There were no takers. After all who coded in VXML :) So when Twilio launched and we saw them take off, we immediately realized tha...