Decoding Product Frameworks That Helped BigBasket Log $1 Bn In GMV
05 November 2024
It was June 2014. Bengaluru, India. The country’s fledgeling online grocer BigBasket’s business was growing at 15% month on month. New product features were ideated and added every morning. And coding was completed by the end of the day. This rapid development was essential to attract more customers, but the downside was scary. Bugs were coming up fast in the technology stack that went unchecked due to tight deadlines.
The problem finds a mention in the book, Saying No To Jugaad: The Making Of BigBasket, penned by T.N. Hari and M.S. Subramanian (both are currently working for the company). Disturbed by the everyday glitches, Pramod Jajoo, then chief technology officer of BigBasket, called Tejas Vyas to his cabin. Vyas was a young tech leader, working with the organisation at the time.
“In the interest of speed, the quality of architecture had suffered. The quality of documentation was just as bad. When an engineer quit, there was no way to understand why something was architected or configured the way it was. One could not be sure what all would be affected if you tweaked a particular part of the monolith,” the authors noted.
It was June 2014. Bengaluru, India. The country’s fledgeling online grocer BigBasket’s business was growing at 15% month on month. New product features were ideated and added every morning. And coding was completed by the end of the day. This rapid development was essential to attract more customers, but the downside was scary. Bugs were coming up fast in the technology stack that went unchecked due to tight deadlines. The problem finds a mention in the book, Saying No To Jugaad: The Making Of BigBasket, penned by T.N. Hari and M.S. Subramanian (both are currently working for the company). Disturbed by the everyday glitches, Pramod Jajoo, then chief technology officer of BigBasket, called Tejas Vyas to his cabin. Vyas was a young tech leader, working with the organisation at the time. “In the interest of speed, the quality of architecture had suffered. The quality of documentation was just as bad. When an engineer quit, there was no way to understand why something was architected or configured the way it was. One could not be sure what all would be affected if you tweaked a particular part of the monolith,” the authors noted.
Stay Connected, Stay Informed –
Don’t miss out on exclusive updates, market trends, and real-time investment opportunities. Be the first to know about the latest unlisted stocks, IPO announcements, and curated Fact Sheets, delivered straight to your WhatsApp.