HNHacker News
TopNewBestAskShowJobs

sridharvembu

1,049 karma · joined January 6, 2008

submissionscomments
sridharvembu··on Zoho: Thriving Amid the Giants
I meant mostly at the high school level. Particularly in the "high end" school districts. Loads of home work, drills, competitive test taking ... because, you know, the Chinese/Koreans are all "way ahead" and score so well in international competitive examinations. I would ignore those examinations (frankly I would ignore the spelling bee too!) but newspapers love such stuff, and scare the middle-class with "we are falling behind the Asians".

College hasn't gone Asian-style yet in the US.

The reason I bring that up is that due to the way the Indian IT sector works, we don't get the best test takers (they are grabbed by the big brand name service companies). So we get people who generally did't do well in various kinds of tests. I count that as a blessing :-)

sridharvembu··on Zoho: Thriving Amid the Giants
We were hunting for a domain in 2003 for our new initiative. We tried variations of SOHO (small office home office). Zoho happened to be up for sale. I was reluctant to shell out the $5K (I am cheap), but Raju Vegesna, persuaded me we should buy it. He was right.
sridharvembu··on Zoho: Thriving Amid the Giants
I was always fascinated by Japan, particularly in the context of India . After we started, I started looking closely at Japanese companies as role models. They had figured out stuff over the years that is unbelievable. Even today, there exist some technologies that pretty much only the Japanese do well (and not only in well known industries). Take a look at this company for example: http://www.uniontool.co.jp/english/product_index.html

They make drill bits for printed circuit boards, drill bits finer than human hair, drill bits you cannot even see with the naked eye.

The magic is years and years of patient, painstaking work, with occasional inspired leaps. That was good to know, particularly when we tended to get bored or tired.

sridharvembu··on Zoho: Thriving Amid the Giants
We plead guilty to having a fragmented suite - that was the price of rapid evolution. But they are coming together nicely now. Check in on us every few months (seriously!). We hope to surprise you.
sridharvembu··on Zoho: Thriving Amid the Giants
I think he meant funding from already profitable products. If that is what he meant, that is true. Zoho quietly got funding from our own earlier products, which got funding from our even earlier products, and so on, until we reach http://www.webnms.com/snmp/ which was bootstrapped ... :-)
sridharvembu··on Zoho: Thriving Amid the Giants
An even better term for us is "and Indian company with an American HQ" - in early days due to foreign exchange restrictions in India, it was painful to have the HQ in India. Increasingly that has faded as India has liberalized. We just imported a ton of Macs for our development team in Chennai; 10 years ago that would have sucked, now it is easy.
sridharvembu··on Zoho: Thriving Amid the Giants
Mix of both. Growth curve shifted back n years (in my case 8 years - I did a PhD too, whose main utility was in coming to the US and then realize that PhD was a waste of time - all I can say is that I am a bit slow!). And those were some of the best years, so there is a fundamental change in the growth curve also.

The thing I most admire about America is the can-do spirit. I am sad that the education system in America is "Asianizing" rapidly, in the spirit of "We have to compete with the Chinese/Koreans/Indians ..." That's not what got America to where it got - it was the can-do "hacker" ethic, and the climate of freedom where that ethic flourished.

sridharvembu··on Zoho: Thriving Amid the Giants
Re: lack of quality, it is a classic "early days" problem. 1950s Japan had a reputation much like made-in-China has today. It is amazing Japan is synonymous with quality today.

It is easy to explain: in a mature economy, any new company would have a mix of experience and new talent. In an emerging economy, practically everyone is a rookie, regardless of age. There are entire million-plus population cities in India where no one, literally not one person, would have any experience in how to manage a 10 person technology project.

The only way to figure stuff out is to make mistakes. Quality is an emergent property coming out of experience. And that is the reason societies don't go from $300 GDP to $30K GDP in 1 year, though it would be possible to carefully mix an immigrant group coming out of a $300 GDP area into a $30K GDP area, and as long as the mixing is at a controlled rate, it is possible to boost the per-capita GDP of the immigrant group very high in a very short time (Indians in the US offer a good example). That is the extra value added by experience of having done stuff.

sridharvembu··on Zoho: Thriving Amid the Giants
Very organic ... 5 after first year, 100 by 4th, 350 by 7th, 1000 by 13. Steady stream of recruiting over time, no huge bump, except in year 2000, when our revenue tripled, thanks to that bubble. But even in that year our headcount did not keep up with revenue - we simply weren't set up to recruit like that. So that was a very stressful year. Then we had many years of stagnation, as the bubble burst and we had to find new things to do. Zoho eventually came out of that period of stagnation and misery.
sridharvembu··on Zoho: Thriving Amid the Giants
When I was in IIT in the late 80's, the hot topic was brain drain out of India. So it is interesting we are talking about returnees now. As the Indian economy liberalizes, talent naturally stays home to pursue opportunity. In any case, India could export a lot of talent, and still not run out (!) - so I never worry about the "drain" part.

On returnees, it is harder the longer someone has been out of India. Two of my brothers returned and they are doing really well (both start-ups http://vembu.com and http://gofrugaltech.com ), but they didn't stay in the US much at all.

My advice: if you are returning, assume that you never left. Lower your expectations (in every way), you will find it easy to exceed them. Traffic is chaotic, civic administration sucks, water problems and so on. But there is something else to India ... the interesting part for me has been that in such poor surroundings, I have always enjoyed a very intellectually stimulating atmosphere. I still can't explain that part.

sridharvembu··on Zoho: Thriving Amid the Giants
It is worth elaborating on bootstrapping. When we started, the hottest tech company in the world was Netscape, and Yahoo was still an infant. So you can see how long it has taken us - nothing much happens to you in 1 year, 2 years and so on. The only thing we had going was patience. It helped that I was educating myself about Japan.

We didn't set out with the mission of bootstrapping. It was sheer necessity: we had no big ideas (only some little ideas), and had no way of impressing anyone to put money on us. Our very first product was this: http://www.webnms.com/snmp/ - the amazing part is we still make money on it! But sexy it isn't - a VC who stumbled on us told us "Why are you focused on such a tiny market?"

By the time money was offered to us, we didn't need it, and we were having too much fun building stuff to even bother pitching to VCs. We came close to a VC round once in 2000: a term sheet was offered. There were things there I didn't like and I was too lazy to negotiate with them, so I simply let it die.

sridharvembu··on Zoho: Thriving Amid the Giants
I am in India now, so was sleeping as this thread happened :-)

I hang out at Hacker News a lot, in fact, almost everyday I send an article to someone or other in the company. I strongly recommend it internally - I love HN (thanks, pg!).

To answer some of the questions: Zoho Corp used to be known as AdventNet. It was bootstrapped from the beginning (1996). Zoho is the latest and the fastest growing division; while we do not reveal our revenues, all I can say is that we are very happy where the Zoho division, as well as the whole company, has gotten. We have solid profits, which we invest in doing interesting new things.

Bootstrapping works, but you have to be very patient. It has taken us 13 years to get here. The fun part is that we now have the human capital as well as the financial capital (the first part is more important) to do a lot of interesting things, and we don't have to worry about VCs or Wall-Street (not that there is anything wrong with them ;-))

On the product side, Zoho has been evolving rapidly, reaching that polish and maturity in stages. If you had tried us 2 years ago, I wouldn't blame you for giving up on us. We are far, far better today - one proof point is that our company, of about 1000 people, has moved to Zoho almost entirely. There are some small bits and pieces that are not on Zoho, but by end of 2009 everything should move. The tools we use extensively within include Mail, Office suite, CRM, Project Management, Meetings, Creator ... just to give an example, we run well over 100 web meetings a day on Zoho Meeting ourselves. We used to pay WebEx about $25-30K per month, and our usage on Zoho Meeting would cost us about $3-4K if we were to charge ourselves. I say that to explain why we have paying customers.

Why the diversified suite? It is not only diversification, it is also a source of differentiation. We believe we can create very compelling integration scenarios that bring substantial productivity increases. One recent example is our Zoho CRM + Mail integration, which has sold over 1000 customers in the 8 weeks or so it has been released. You will see many more such things rolled out, partly addressing the criticism that it has been a fragmented suite.

So how do we do it? Silicon valley style flexible culture mated with Japanese style patient engineering. There are huge lessons to learn from Japan's post-War leap. As one example, Japanese companies (the giants of today) always had a train-your-own-talent policy. Their colleges most certainly didn't do it - for the most part, college in Japan is considered relaxation time before the real work begins. We dispense with what I believe to be non-essential parts of Japanese experience, like the rigid discipline, substitute it with silicon valley style flexibility.

The one achievement I am proud of is not a product or technology: it is our "University" (as we call it) where we recruit and train 17 year olds - the typical school leaving age in much of India. About 100 of our 1000 employees have come from that program now, and it is growing fast. Longer term, we should get 30-50% of our talent pool directly out of high school.

I have written extensively about it. Let me summarize: I do not believe in college. I believe most real education happens in the work-place, an observation Peter Drucker made originally. I regret going to college myself - we would have been 10x bigger if I hadn't gone to college, so that is my opportunity cost. I probably wouldn't have if I had grown up in America.

Sorry for the long comment. I wanted to answer all the posted questions in one shot.

sridharvembu··on Let's Abolish High School
I came to the same conclusion (based on my own experience in teenage, and observations later) that there is a lot of talent waiting to be tapped in teenage years, and treating teenagers respectfully as young adults and giving them responsibility is good for them and good for society.

That is one of the reasons we like to hire 17 year olds in Zoho and combine education with work. Labor laws won't let us hire any sooner, but if it were my own family members, I would hire them sooner.

sridharvembu··on Why IT Happened in Southern India, an Unorthodox Explanation
"To my ears this sounds incredibly bureaucratic and unnecessary when you work with competent people"

Here is my explanation based on my observations.

- The mass expansion of IT in India, particularly in its second decade (late 90's to the present) was the result of the series of credit bubbles in US. Similar to China's manufacturing export bubble. Without the US bubble, the expansion would have happened, but not in the reckless, pell-mell fashion it happened.

- As a result, Indian IT companies hired fresh-out-of-college people in massive, really massive numbers - 25,000 people a year in each of the big 4 companies. Private colleges expanded massively to meet that demand. The analogy is to the US housing expansion (ultimately both were caused by the credit bubble).

- Competence arises for a good part from experience. To visualize this, do a thought experiment: how would your team look if you substitute every team member with the same person but as they were starting out fresh. A good part of competence is simply knowing the skill & aptitude make-up of every team member. When everyone is fresh, that vital knowledge is absent.

- So the Indian industry came up with a "solution" so fresh recruits don't cause too much damage: create rules and procedures for everything. Bureaucratize. Alas, that "solution" imposes a long term toll on culture of the company.

sridharvembu··on Why IT Happened in Southern India, an Unorthodox Explanation
Badri, I have a more radical argument: quality of education is irrelevant for the most part. Ultimately the real task of education (i.e imparting knowledge) is borne by the employer or done as a by-product (sometimes an accidental by-product) of a job. What the system achieved was a little bit of IQ filtering, a whole lot of placebo ("building confidence"), and an employer willing to offer a job to these graduates because they were "qualified". What most employers didn't realize was that most candidates became qualified because they were placed on a job!

If what I say above is true, we could dispense with the college and deliver the placebo faster and cheaper. Based on that premise, we performed the experiment at Zoho: we recruit directly out of high schools, and train people ourselves. I am happy to report that it works - which lends more evidence to the college-as-placebo hypothesis.

sridharvembu··on India's school for the poor but gifted
This is exactly what happened in the southern state of Tamil Nadu. In 1985, when I finished high school, there were less than 10,000 seats in the whole state of (about 60 million people). Today, there are more than 150,000. Today, practically any kid that wants to attend an engineering college can get into one, and many seats actually go unfilled. The quality of the education is spotty, but really, what this education achieved is a kind of placebo effect - give confidence to people, which is what Kumar also describes. This explosion in number of colleges directly played a role in the emergence of the IT industry, which is primarily based in southern India.

I wrote about it in 2006: http://blogs.adventnet.com/svembu/2006/01/19/a-not-so-brief-...

I reposted it now at Zoho: http://blogs.zoho.com/general/why-it-happened-in-southern-in...

sridharvembu··on India prays for rain as water wars break out
India built a vast distributed system of small reservoirs - also known as village ponds or temple ponds. The fact that the rural system of governance was dismantled (and they realized the problem, and tried to reassemble it in a pale imitation) led to the neglect of these ponds, among other issues.
sridharvembu··on India prays for rain as water wars break out
This is a quote from the article: "India's vast farming economy is on the verge of crisis. The lack of rain has hit northern areas most, but even in Mumbai, which has experienced heavy rainfall and flooding, authorities were forced to cut the water supply by 30% last week as levels in the lakes serving the city ran perilously low."

Heavy rainfall and flooding followed by severe drought. This is a standard pattern across India, not just in Mumbai. Indian villages always have had water storage ponds - in fact most Hindu temples have a pond attached to them, which serves to recharge the ground water level in the whole village.

What happened in the last 40+ years is a complete dismantling of traditional village governance, initially replaced with State-government appointed government bureaucrats (almost all of whom didn't reside in the village they were supposed to administer and rarely even visited it) and then much later, an elected village body that has few real powers, and still answers to a State-appointed bureaucrat.

It was all done with the best of intentions. But it ended up centralizing rural administration - destroying the village in order to save it. Simple tasks as desilting the water storage ponds were neglected, and eventually many of those ponds were encroached upon. This is true everywhere in India, in major cities as well as small villages.

So it is not simply just nature that is the problem here.

sridharvembu··on Autism and Programmers
For your information, the government recently legally conceded a case of autism-vaccine connection where the parents (both medical professionals) had a perfect record of their daughter's medical history.

Keep down-voting me; but if you have a kid, please, please investigate this before you accept conventional wisdom.

sridharvembu··on Autism and Programmers
This whole autism-geek connection is a useless myth. I have a son with autism, and we know a lot of parents with autism. Parents come from every income range, social class, profession and "geek orientation".

And contrary to another myth, most autistic kids (the vast majority) have no savant skills. It is a disease. The ones who recover do tell how they felt trapped inside.

For those of you who have young children or planning to have children, here is a suggestion: investigate just how many vaccines we are giving kids these days, and compare that to how many were given 25-30 years ago. Educate yourself - I wish I had. I trusted the "system" implicitly, without realizing that the average doctor and certainly the average pediatrician is an unthinking protocol pusher. The average pediatricians typical workload could be automated. Enough said.

sridharvembu··on "Francisco's Money Speech" by Ayn Rand
I read this last time 20 years ago as an undergraduate student in India, and I still find it inspiring after all these years.

I find it particularly relevant today, when the Federal Reserve and the government are intent on destroying the moral foundation of money. I expand on it at: http://blogs.zoho.com/general/money-as-a-moral-institution

sridharvembu··on The Future of SQL in a SaaS world: Announcing Zoho CloudSQL
For convenience, the JDBC client API is available at:

http://zohoreportsapi.wiki.zoho.com/Java-Client-Library.html

The Google AppEngine version of Python library is at: http://zohoreportsapi.wiki.zoho.com/Google-App-Client-Librar...

Stand-alone Python library is at: http://zohoreportsapi.wiki.zoho.com/Python-Client-Library.ht...

sridharvembu··on The Future of SQL in a SaaS world: Announcing Zoho CloudSQL
Can you tell us which ones you tried? I apologize for this opening day glitch.
sridharvembu··on The Future of SQL in a SaaS world: Announcing Zoho CloudSQL
(I am the CEO of Zoho) Let me provide some context on this. What we are doing is to separate the two layers in a database that have traditionally been so welded together that you don't even think of them as two layers: the SQL processing "logical" layer and the storage "physical" layer.

Our real technology here is a multi-dialect SQL processing engine, which can handle a wide variety of SQL dialects with ease (ANSI, Oracle, SQL Server, DB2, MySQL, Postgres being the major variants). At AdventNet, we have offered a product called SwisSQL to companies, for SQL migration, conversion etc. for a while (4+ years now). We couple that technology with physical storage or other APIs underneath.

Once you decouple the two layers, a lot of possibilities open up. The "slow, risky, inefficient" part is really a function of how efficient the middleware is in processing a variety of SQL dialects and translating it to what the physical layer needs.

SQL is the mainstay of business information processing. We are using the standard everyone loves (or loves to hate in some cases!) and bring it to the cloud computing era. Our goal is to preserve compatibility for existing applications - hence our JDBC driver etc. - while drastically lowering the cost. Today's announcement is only the first step on a long road ahead.

To add a hacker news dimension, I have long been fascinated with relational data modeling. I have always believed that welding together storage with relational models was a disservice to Codd's brilliant work. There are a lot more ways in which relational modeling power can be exploited without tying it so closely to a specific storage context.

sridharvembu··on The French cafe is dying
Disclaimer: I don't know anything about France

This is a response to PG's comment about social, behavioral change. It is worth understanding the fundamental economic underpinning of this.

Two observations or assertions: a) People have more debt than a generation ago b) People have less leisure today than a generation ago.

These two assertions seem broadly true world-wide. As an example, young people can observe how many of their college-educated peers are graduating with excessive levels of debt. These two are connected - in fact, I believe (a) causes (b), to the extent that you can determine causation in social science.

Now who caused (a) i.e the culture of debt? Answer: Government policy, in particular central bank policy. Ultimately, money is credit in a fiat system, so when we talk about "Fed creating money out of thin air", they are really creating credit (i.e debt instruments) out of thin air. Eventually, cascading layers of debt entraps most of the population - corporations and individuals alike.

Debt causes serious cultural and social changes. Keynes had this right:

There is no subtler, no surer means of overturning the existing basis of society than to debauch the currency. The process engages all the hidden forces of economic law on the side of destruction, and does it in a manner which not one man in a million is able to diagnose.

sridharvembu··on Gay marriage: the database engineering perspective
Here is fully normalized relational model. I will adopt a simple notation

Table: <PrimaryKeyID>, Column1, Column2

where the <> denotes the column to be primary key and Column1, Column2 etc. denote regular non-key attributes. The notation ForeignKeyID from SomeTable denotes a foreign key referring to a row in SomeTable.

Persons: <PersonID>, Name, DateOfBirth

Men and Women are defined in separate tables, to enforce integrity constraints later, which is why it is not modeled as a Gender attribute in Persons table. These tables have no attributes, simply a listing of men and women. It is a perfectly valid relation that has only one column, by the way. Note that the foreign key here is also the primary key of the table.

Men:<PersonID from Persons>

Women: <PersonID from Persons>

This represents a basic marriage, the only attribute of which is the date. Many specific forms of marriage are captured below.

Marraiges: <MarriageID>, DateOfMarriage

MarriageID is the primary key for the tables below. The design below permits polygamy, so further integrity constraints would be needed to restrict it. If a marriage is not permitted to be dissolved and no polygamy is permitted, we can place a uniqueness constraint on both Men and Women attributes below. If all types of marriages are permitted in all jurisdictions, these 3 tables below could be unified.

ConventionalMarriages: <MarriageID from Marriages>, PersonID from Men, PersonID from Women

GayMarriages: <MarriageID from Marriages>, PersonID from Men, PersonID from Men

LesbianMarriages: similar to above

Notice how a marriage has to exist for a divorce to exist

Divorces: <MarriageID from Marriages>, DivorceDate

Some features of the model: if a person A & B marry and then they terminate a marriage, and remarry again, it gets a new marriageID.

Some integrity constraints:

a) Zero or One marriage at a time rule:

If a PersonID occurs more than once in the Marriages table, then order the marriages by marriage date, order Divorces by DivorceDate, and enforce the rule:

  for all except last MarriageID in Ordered(Marriages), ensure Divorces(MarriageID) exists, and DivorceDate(MarriageID) < MarriageDate(next(MarriageID))
 
b) Polygamy would require more complex integrity constraints.

The nice thing about thinking about the problem relationally is that you focus on the data and its interrelationships, and avoid language considerations. Notice how a fully normalized relational model captures a lot of the constraints automatically, and only the most complex of constraints need to be separately stated.

Finally, note that this is an abstract model and should be separated from details of storage.

sridharvembu··on PE Obama’s 1st Big Mistake
I would agree if you said "most economists" instead of "all". On the minimum wage, a couple of Princeton economists wrote a scholarly paper pointing out how that didn't suppress hiring (sorry, don't have a handy reference) or increase unemployment. On barriers to hiring/firing, I grant that most economists would agree they are bad.

On the other hand, Krugman himself has been a strong advocate of nationalized health care. Milton Friedman argued how the health care problem is really one of licensing regulations designed to maximize pay for doctors. Imagine an American Software Association that decides how many licenses to grant every year, and you need those credentials to be a hacker. Yes, Friedman addressed the "quack" argument too.

sridharvembu··on PE Obama’s 1st Big Mistake
I had the same thought as Mark Cuban. A PhD in Economics, even winning the Nobel Prize (see my critique of Krugman) doesn't give you the real world feel that starting and running a business does. Economics is full of unintended consequences. Couple of examples, which every start-up person here can appreciate: if you make it very hard to do a lay-off, that leads to businesses becoming extremely cautious in hiring. The minimum wage directly leads to entrepreneurs not taking a chance to hire a less skilled person and train them on the job. These are easy enough to see when you run a business.

It would amaze you how many things that are "common sense" for an entrepreneur are hard for someone sitting in their ivory tower.

This is not just a problem in economics. After I got out of Princeton with a PhD in Electrical Engineering, it amazed me just how orthogonal to the real world much of my adviser's academic work proved to be - I happened to land a job that directly dealt with one of his core areas of research, though I wasn't involved in that area during my PhD myself. My realization led me to write a paper that pointed out that his work was dealing in mathematical models that were not very relevant to the real world, which predictably led to our intellectual parting of ways.

I felt experience working as an engineer should be mandatory for anyone aspiring to be an engineering professor, yet you will find that most engineering faculty have never worked outside of academia.

sridharvembu··on Data is good, code is a liability
I believe we need a "converse of Lisp" - in Lisp code is data, I believe what we need is the notion "data replaces (most) code". That leads to the question, what really is data, and I believe Codd supplies the best answer to that question. One of the truly original ideas in Computer Science that post-dates Lisp (and is not anticipated by Lisp) is Codd's relational model of data, which is not to be confused with relational databases used for storage.

Note that Codd's model is not Turing-complete, while all but the most trivial definitions of code lead to Turing-complete systems, hence the parenthetical most in my "data replaces (most) code". Data is easy, code is hard could be another way to state that.

We have experimented with such ideas, and we can report that they do significantly improve clarity and therefore productivity.

As an aside to a pg essay, I believe clarity is not the same as succinctness and as a corollary, succinctness does not imply productivity except in the somewhat trivial sense of ease of typing.

sridharvembu··on Mr. Benioff, Tear Down That Wall
Thanks folks, as a Hacker News regular, I am truly honored to have this featured here.

To address lhorn, this post was written and made it to HN when our India folks were asleep (13.5 hour time difference). And it may be hard for you to accept, but our company doesn't operate that way - the kind of "astro-turfing" you describe. I post at least once a week on Zoho blogs, and this is probably the second time ever anything made it to HN. And it was not a personal rant - it is about a major software-as-a-service vendor who acts in ways totally contrary to their public posturing. Keep in mind, they invited us to be there on AppX, and we did the integration work with their support. As the CEO of Zoho, I deal with hundreds of companies, large and small, in relationships that succeed and in relationships that fail to materialize. What happened with Salesforce was unusual enough to warrant calling out - and should be a cautionary tale for other companies.

← PreviousPage 3 of 4Next →