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.

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 get s

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

KooKoo Contact Center integration with WhatsApp

WhatsApp announced the launch of their business API yesterday. This is a big deal. A lot of businesses have been asking for WhatsApp integration and now its a possibility. Twilio has already launched an integration . Won't be long before we see a lot more integrations pop up. The most obvious use case is for support chat bots, alerts and reminders. But we at Ozonetel believe one other use case will become the dominant use case, WhatsApp as a support channel with human agents. We believe WhatsApp will become a dominant channel in contact centers world wide. There are multiple reasons for this: WhatsApp is ubiquitous. Everyone has the app. WhatsApp interface is well known to all customers. It is feature rich. You can share audio, video, location etc in the app itself. You can integrate bots for repetitive tasks. Being the leaders in cloud contact center solutions, we at Ozonetel knew that we had to integrate with the WhatsApp channel as early as possible.

Cloud Telephony Experiments

Search This Blog