APLawrence - Information and Resources for Unix and Linux Systems, Bloggers and the self-employed
RSS Feeds Get APLawrence.com by RSS











(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Home > Girish Venkatachalam > Eat the Mango
Printer Friendly Version




Eat the Mangoes




by Girish Venkatachalam

Girish Venkatachalam is a UNIX hacker with more than a decade of networking and crypto programming experience. His hobbies include yoga,cycling, cooking and he runs his own business. Details here:

http://gayatri-hitech.com
http://spam-cheetah.com

Mango is a delicious fruit. You will know how it tastes only when you eat it.

You will see that I am not meandering. What I say is very much to the point. Long ago there were a bunch of "scientists" who were doing research on mangoes. They measured the length of mango twigs, they measured the angle of shadows created by mango trees, they looked the soil and conditions for growth of mango trees. They were doing a PhD dissertation on the wonderful fruit.

When all this was going on, a guy came and simply started eating the mangoes. The researchers wondered what this guy was up to. Only when the guy told these scientists that the mango tasted very good these scientists tasted the fruit.

Why am I saying all this? What is the analogy?

I should mention this famous OpenBSD statement. It is attributed to OpenBSD devs, but I have no idea who came up with this. It goes like this.

Shut up and code.

What is the use discussing the design and making long architecture documents? All it takes is working code! Nothing else matters when the code does its job!

We should taste the mangoes. Mango is a fresh luscious fruit, very sweet and delicious. Another great analogy is this. An ass that carries a sac of sugar on its back does not know the taste of sugar. It does not even know that it is carrying such a sweet substance in its back.

Similarly we waste a lot of time talking, arguing, researching when we should be doing coding. We should validate our design idea with simple prototype code. Companies that get this aspect right get everything else right in due course.

I understand that complex projects need a lot of discussions and design before execution. I don't disagree at all. But should we be spending time talking or doing?

We should taste the mango. If the mango tastes good, then everything else must have been good automatically. There is no need to look into the details when the end result meets our expectations.

Another interesting quote is this. I like this one. The proof of the pudding is in the eating. Everything else becomes irrelevant the moment you have working code that is stable and does its job.

Let us eat the mangoes. And leave others to do the research.


If this page was useful to you, please click to help others find it:  
Your +1's can help friends, contacts, and others on the web find the best stuff when they search.


4 comments




More Articles by Girish Venkatachalam



Click here to add your comments





Wed Sep 9 10:55:14 2009:   TonyLawrence

gravatar
There are detail people, and grand overview people. The world needs both, but these two types can really tick each other off.





Fri Sep 11 06:10:50 2009:   MichielOvertoom

gravatar
Joel Spolsky names them 'Architecture Astronauts'; see http://www.joelonsoftware.com/articles/fog0000000018.html

On the other end, if you want to add a certain feature to Python, it's not enough to just come up with the idea. You have to give an implementation, too.



Tue Sep 29 05:48:07 2009:   Arun

gravatar
Nice article.
But nature has an advantage - Time. The mango probably became as delicious as it is today in a million years. Evolution. We don't!



Tue Sep 29 12:32:37 2009:   TonyLawrence

gravatar
Well, we've had half a million years of evolution - and have come a bit farther than mangoes :-)

Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



LOD Communications, Inc.

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.


My Troubleshooting E-Book will show you how to solve tough problems on Linux and Unix systems!


book graphic unix and linux troubleshooting guide




Buy Kerio from a dealer who knows tech: I sell and support

Kerio Connect Mail server, Control, Workspace and Operator licenses and subscription renewals