<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vivek Vaidya on Medium]]></title>
        <description><![CDATA[Stories by Vivek Vaidya on Medium]]></description>
        <link>https://medium.com/@vsvaidya?source=rss-718d5493dd86------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*9UJYOAZ5G5QDxpZTcT0p-w.jpeg</url>
            <title>Stories by Vivek Vaidya on Medium</title>
            <link>https://medium.com/@vsvaidya?source=rss-718d5493dd86------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:16:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vsvaidya/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Ketch — The Back Story]]></title>
            <link>https://vsvaidya.medium.com/ketch-the-back-story-6c4ef44f7f86?source=rss-718d5493dd86------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c4ef44f7f86</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[ketch]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Vivek Vaidya]]></dc:creator>
            <pubDate>Fri, 26 Mar 2021 04:56:53 GMT</pubDate>
            <atom:updated>2022-04-22T15:42:19.001Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ketch — The Back Story</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CEZCPH8gxaEwfJ5qIaDVpQ.png" /></figure><p>Every start-up has a back story. So does Ketch. And this one is personal.</p><p>To understand why, we’ll need to rewind back to early 2017. Salesforce’s acquisition of Krux had closed a few months earlier and the “integration” process was kicking into 3rd gear. Having lived through various incarnations of ePrivacy, Safe Harbor, Model Clauses, etc., I was intimately familiar with how to build data management systems where user level data moved back and forth across the Atlantic, at least in a digital sense. But then came GDPR. And my entire world-view on how to store, process, and manage data shifted radically.</p><p>A few months into my tenure at Salesforce, I found myself leading the Engineering team for Salesforce Marketing Cloud and with May 25th 2018 fast approaching, GDPR compliance became the top product priority for me. Every product within Marketing Cloud had its own tech stack and while I was overseeing the development of all products, I was — as expected — deeply involved with the solution design for GDPR compliance in the Krux platform.</p><p>In GDPR parlance, Krux operated as a Data Processor with our customers being Data Controllers — the latter being a fancy legal term for businesses that have a direct relationship with end-users (or data subjects) and the former being companies that provide (software) services that manage and process user data on behalf of the Controllers.</p><h3>Consent Management</h3><p>GDPR requires businesses to operate with a “consent, opt-in” mindset — meaning that any end-user data that is used by a business can only be collected and used if the end-user has given the requisite consent. GDPR also requires businesses to explicitly declare the purpose(s) for which they are collecting user data and allow users to control if their data is used (or not used) for a given purpose.</p><p>Therefore, the first challenge for Krux was the collection of consent. Krux didn’t have a direct relationship with consumers so we had to provide a way for our customers to pass on the consent signals that they were collecting from their users. Consent Management Platforms had not cropped up yet so we ended up building a Consent Management API that was exposed to customers via our JavaScript tag, Mobile SDKs, and an HTTP(s) end-point. Some customers were not ready to use the Consent Management API in any form so we also provided the ability to upload consent signals using files uploaded to S3.</p><p>Once the consent signals had been collected, we had to put them to use. Before we could do that though, we had to figure out the most recent consent signature (think of the consent signature like a bitmap — a sequence of 0s or 1s with 1 place, or bit, for every data processing purpose in the Krux platform) for every user. The most-recent consent signature logs were rolling in nature — in other words, we had to retain the consent signature for every user regardless of when that user generated any activity for a given customer. <strong>Writing the map-reduce job to do this wasn’t hard, but the fact that we had to run it every day, for every customer made a material impact on our AWS costs.</strong></p><p>Next, we had to assign a data processing purpose to each and every data processing job and then update the job to respect the consent choice made by the user.</p><p>As an example, consider the following query for the purpose of Analytics, which counts the total number of users generating at least 1 page view broken down by “site” for a given customer (each customer got a unique organization_id in the Krux platform):</p><pre>SELECT event_site, COUNT(DISTINCT krux_user_id) <br>FROM user_events <br>WHERE <br>  organization_id = &#39;0xDEADC0DE&#39; AND <br>  event_type = &#39;PAGE_VIEW&#39; AND <br>  DATE_DIFF(now(), event_day) &lt;= 30 <br>GROUP BY event_site</pre><p>To comply with GDPR, the above query had to be rewritten like so:</p><pre>SELECT ue.event_site, COUNT(DISTINCT ue.krux_user_id) <br>FROM user_events ue, user_consent uc<br>WHERE <br>  ue.organization_id = &#39;0xDEADC0DE&#39; AND <br>  ue.event_type = &#39;PAGE_VIEW&#39; AND <br>  DATE_DIFF(now(), ue.event_day) &lt;= 30 AND<br>  ue.organization_id = uc.organization_id AND<br>  ue.krux_user_id = uc.krux_user_id AND<br>  uc.consent_purpose = &#39;analytics&#39; AND<br>  uc.consent_value = True<br>GROUP BY event_site</pre><p>That looks straightforward enough. And for simple use-cases like that, it was. But Krux had a large number of fairly complex data processing jobs that were implemented using Hadoop and/or Spark which were not so straightforward to modify. The brute force approach worked in some cases, but in most cases, because performance could not degrade too much (or at all), we had to figure out clever ways of implementing that “join” in a cost-effective, efficient manner.</p><h3>Rights Management</h3><p>Under GDPR, a data subject (legal term for a consumer or user) can exercise multiple rights. The two that were most relevant for us were: RTBF (Right to be Forgotten) and Portability — or, in plain English, delete my data and give me all my data, respectively.</p><p>On the surface, this seems simple — just issue the following queries:</p><p>For RTBF:</p><pre>DELETE FROM user_data_table <br>WHERE <br>  customer_id = &#39;0xDEADC0DE&#39; AND <br>  email_hash = sha256(‘0xdeadbeef@dabbad00.com’)</pre><p>or, for the Soft Delete and/or Data Obfuscation peanut gallery:</p><pre>UPDATE user_data_table SET <br>  email_hash = sha256(&#39;gobbledygook&#39;), <br>  gender = &#39;other&#39;, <br>  age_range = &#39;other&#39;, <br>  household_income = &#39;other&#39;, <br>  customer_status = &#39;other&#39;, <br>  is_deleted = True <br>WHERE <br>  customer_id = &#39;0xDEADC0DE&#39; AND <br>  email_hash = sha256(‘0xdeadbeef@dabbad00.com’)</pre><p>And, for Portability:</p><pre>SELECT gender, age_range, household_income, customer_status<br>FROM user_data_table <br>WHERE <br>  customer_id = &#39;0xDEADC0DE&#39; AND <br>  email_hash = sha256(‘0xdeadbeef@dabbad00.com’)</pre><p>If only it were that simple. If you have a modern data technology stack like we did at Krux (most companies fall into this category now), user data was spread across multiple types of data management systems:</p><ul><li>Raw Log files in Blob Stores (S3)</li><li>Processed, semi-structured data sets in Blob Stores (S3)</li><li>NewSQL Data Warehouses (Redshift)</li><li>NoSQL Key-value Stores (DynamoDb)</li></ul><p>Our data technology stack had grown and scaled organically and while we weren’t moving fast and breaking things, we were definitely moving fast. Which is to say that we didn’t have all of the metadata about our various data assets stored in a centralized Data Catalog that we could easily query to figure out which S3 locations, Redshift tables, and DynamoDb tables we had to process in order to retrieve or delete all the data for a given user.</p><p>The process of discovering all the data assets that we had to query to delete or retrieve user data was painful. A significant amount of time went into that. Not to mention all the extra AWS data processing costs we incurred to do the discovery.</p><p>All in all, the GDPR compliance project consumed 6 of our top-notch engineers for just over 6 months. While that cost was significant, it paled in comparison to the <strong>30 % increase in our AWS costs.</strong></p><h3>And now, Ketch</h3><p>Which brings us to Ketch, where we are building a Data Control Platform that provides</p><ul><li>A <strong>Policy Center</strong> that allows our customers to maintain a centralized repository of privacy compliance and data governance policies</li><li>A true <strong>Consent Management Service</strong> that allows our customers to configure their privacy posture via the Ketch Policy Center, present a Privacy Experience to capture consent consistent with that posture</li><li>An <strong>Orchestration Engine </strong>that allows our customers to define workflows that manage the flow of data subject rights (DSR) requests <strong><em>and</em></strong> propagation of consent signals to external systems that manage and process user data on their behalf</li><li>A <strong>Data Asset Manager </strong>that discovers and builds a searchable Data Catalog of data assets across all the data management systems — SQL, NoSQL, NewSQL, Blob, Structured, Semi-structured — used by a customer</li><li>A <strong>Data Classification Service</strong> that detects and classifies private and sensitive data, and identifies all the tables, files, partitions, etc. that store personal user data</li><li>A <strong>DSR Automation Service</strong> (the <strong>Ketch Transponder</strong>) built on top of the Data Asset Manager that allows Developers and IT personnel to define customized actions depending on data type (delete, tokenize, mask, anonymize) to address DSR requests</li><li>A <strong>Data Fortification Engine</strong> that enforces data governance policies defined in the Policy Center across all the data management systems used by the customer</li></ul><p>Remember that 6 devs/6 months with a 30% increase in AWS costs — <strong>those numbers would have been halved across the board </strong>if I had access to Ketch’s Data Control Platform, specifically, the Policy Center, the Consent Management Service, and the Data Asset Manager. And if you include the Transponder for DSR fulfillment on data platforms like S3 and DynamoDB, it would have <strong>resulted in cost savings of 75%!</strong></p><p>So, yeah. This one is personal. I am building Ketch for my former self. Ketch is the platform I wish I had access to back in 2017.</p><p>P.S. To keep this post somewhat readable, I have glossed over many of the details of our generalized GDPR design and implementation. If you are curious to learn more or want to discuss this further, please give me a shout!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c4ef44f7f86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Habu — the why and the what of the industry’s first Marketing Data OS]]></title>
            <link>https://vsvaidya.medium.com/habu-the-why-and-the-what-of-the-industrys-first-marketing-data-os-7a6ae2bb7442?source=rss-718d5493dd86------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a6ae2bb7442</guid>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[marketingdataos]]></category>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[thinkhabu]]></category>
            <dc:creator><![CDATA[Vivek Vaidya]]></dc:creator>
            <pubDate>Wed, 12 Feb 2020 21:16:47 GMT</pubDate>
            <atom:updated>2020-02-12T21:16:47.629Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Habu — the why and the what of the industry’s first Marketing Data OS</strong></h3><p>“Another one?” “Really? “. That was my inner monologue as we were discussing whether to jump in the fray — again — and launch yet another MarTech / AdTech company. When <a href="https://www.linkedin.com/in/tommychavez/">Tom</a> and I started super{set}, we set ourselves the ambitious goal of creating category disrupting companies in multiple verticals leveraging our expertise in building AI/ML driven software services and applications and we wanted to flex our muscles in verticals beyond AdTech and MarTech.</p><p>When <a href="https://www.linkedin.com/in/mattkilmartin/">Matt Kilmartin</a> and <a href="https://www.linkedin.com/in/mikemoreau/">Mike Moreau</a> raised their hands and were ready to come on board at super{set}, we revisited the possibility of another MarTech company. Matt brought with him a lot of informed perspective from his ~3 years at Salesforce in the Marketing Cloud sales organization, especially from his role as Chief Customer Officer for the Consumer Engagement Platform. And we were extremely fortunate to have worked with a large group of people who were (and continue to be) very generous with their time and input on the challenges they continue to face in their myriad jobs in Marketing and MarTech. As I compared notes with industry friends, colleagues, and former clients, five themes kept coming up consistently:</p><p>1. The last 10 years saw the arrival (and in some cases, departure) of a plethora of marketing / advertising platforms and/or marketing clouds with lofty and ambitious promises of customer/consumer data unification and seamless integration and interoperability. And while a lot of progress has been made, customer and/or consumer data still sits in siloed systems and the various marketing / advertising systems don’t talk to each other as effectively or efficiently as they could or should.</p><p>2. Cross-channel orchestration remains an illusory goal. One repeated example that came as a surprise to me was around the integration of email and website channels. A customer signs up for a newsletter with a Brand resulting in the customer’s email address being added to the Brand’s CRM or Email Marketing System. Soon enough, the customer receives the first newsletter which contains a list of offers and recommendations from the Brand that are (supposedly) personalized for the customer. The next day, the same customer shows up to the Brand’s website and you would think that the customer would be presented with the same set of offers as the ones sent in email. But what I heard was that this is a challenge for most of the brands that I spoke to.</p><p>3. A very significant portion of a brand’s media budget gets allocated to Google, Facebook, and Amazon. Extracting intelligence from the vast amounts of data generated through those paid advertising is an ongoing challenge for a variety of reasons — some technical, some operational.</p><p>4. All the device graph companies from the last 8 years or so have come and gone and yet brands and media companies have not been able to effectively deploy and implement “Identity Graphs” at scale to solve their most pressing business problems beyond Onboarding and activation of PII based datasets into Facebook, Google, etc. An earlier — younger — version of me would have said, “Great! Let’s build a better Identity Graph and companion solutions and compete with the well-established vendors!”. That wouldn’t have necessarily solved the business problems though. Brands don’t need another Identity Graph — they need plumbing and connectors to take advantage of the already excellent ones that are out there and integrate those Identity Graphs into solutions for their business problems. A case in point is the example above (#2) where the offers presented in the email channel are not connected to the web channel.</p><p>5. And finally, Privacy. GDPR has come and gone, CCPA too. Most marketing and advertising platforms do not have consent management and privacy by design embedded into them on the ground floor as first class citizens. Brands and media companies need to pay special attention to this because CCPA is just the beginning and data protection regulatory frameworks from 14 more states are imminent.</p><p>A sixth theme emerged from conversations with brands and mid to large scale media companies with large technology organizations. I discovered that these companies have spent significant resources to build their own tech stacks to solve some of their business problems related to marketing and advertising. But they had some gaps in their respective solutions and they were looking to fill some of those gaps using a partner. In this scenario, deploying a new mar-tech platform that required all the data to be moved out of the first party data center (private/public/hybrid cloud) into the new platform’s public cloud infrastructure was simply not going to be feasible. Instead, all auxiliary services that filled the solution gaps would have to be deployed in the first party data center.</p><p>At Habu, we decided to adopt a fundamentally different approach in order to address these challenges. We realized that we wanted to provide technology to brands to enhance consumer experiences but do it in a way where, if needed, we could operate as an extension of an existing marketing technology stack / platform. The need for a collection of services that could be assembled together into a platform while being modular enough to be deployed independently has resulted in the creation of the Habu Marketing Data Operating System (MDOS)</p><p>I am a technologist first and sometimes I get cute with (and am quite proud of) my analogies. We’ve embraced micro-services as a core software architecture pattern and just like our API services, MDOS is modular, not monolithic and is designed as a layered collection of services and applications. We speak Docker and Kubernetes and our services and applications can run seamlessly on AWS, GCP, and Azure. A customer has complete flexibility in choosing what services and applications they want to use — all services can be deployed in headless mode and integrated with upstream applications using APIs.</p><p>We’re extremely encouraged by the feedback we’re getting from every conversation we have in the market and our early customer deployments. We’ve also realized that you need a diverse blend of skills and expertise in AdTech <strong>and</strong> MarTech in order to build solutions that can address the challenges facing our industry today. The Habu team has been doing just that for the last 20 years at Salesforce, Microsoft, Google, Facebook, IBM, and Akamai.</p><p>So, yeah. Habu. Another Mar-tech company. Not the platform you were not looking for though.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a6ae2bb7442" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s luck got to do with it?]]></title>
            <link>https://vsvaidya.medium.com/whats-luck-got-to-do-with-it-952d32cd3282?source=rss-718d5493dd86------2</link>
            <guid isPermaLink="false">https://medium.com/p/952d32cd3282</guid>
            <dc:creator><![CDATA[Vivek Vaidya]]></dc:creator>
            <pubDate>Tue, 21 Jan 2020 02:44:03 GMT</pubDate>
            <atom:updated>2020-01-21T02:44:35.441Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4igbsCVbzEcIyXzT05GIkA.jpeg" /></figure><p>“Luck and timing. The success of your startup has as much, if not more, to do with luck and timing in addition to your blood, sweat, and tears. Always remember that.” That was how <a href="https://www.linkedin.com/in/harpal-sandhu-961a774">Harpal Sandhu</a>, CEO at Integral Development Corp. opened his fireside chat with <a href="https://www.linkedin.com/in/tommychavez/">Tom Chavez</a> at our most recent Show N’ Tell at <a href="https://superset.com/">super{set}</a>. It was a great reminder of what’s become one of my top 3 interview questions: “Do you consider yourself lucky? Or, how has luck played a role in getting you where you are?” An answer that I got has stuck with me is, “I consider myself extremely lucky to have been born in the family that I was born in.” That certainly is true for me too and that will be the subject of another post. Which is to say that as I reflect on my life, there is a long list of things that I put down to plain old luck. And timing. Because without the two, I would’ve never met Tom and I probably wouldn’t be where I am right now.</p><p>I moved to the Bay Area in June 1998 from Denver to join a young start-up called Imparto Software. Java was all the rage back then but 14 months in there was talk at Imparto about changing the tech stack to Microsoft COM. Impressionable, passionate, naïve young me didn’t want anything to do with Microsoft so I started looking for another gig. Now, I am a bit more pragmatic and Microsoft has made a lot of progress so I can happily consider using Azure. To keep things interesting and mix things up — ‘cuz why not — I decided to look for jobs in San Francisco, Boston, and Denver.</p><p>Finding recently funded, early stage startups wasn’t as easy in the late 90s as it is now. I spent a lot of time on Craigslist and through that I found a couple of companies in Boston that I liked. One of my ex-professors connected me with a company in Denver that was doing some interesting work building auction based marketplaces for petroleum markets. The other strategy I came up with was to visit the portfolio pages of VC firms like Accel, Kleiner Perkins, Sequoia, Mayfield, Benchmark, etc. and identify newly funded companies. Given my background in Math and CS, I was looking for companies that were building enterprise software anchored in Math. Today, such companies are dime-a-dozen — in fact there’s an entire category of such companies. But back then, it was slim pickings.</p><p>After many, many hours of surfing, I came across a company called Rapt Technologies on the Accel website. And I really liked what I read — Rapt was building software that would help companies like Sun Microsystems optimize their supply chain for components like memory boards, hard disks and processors that were used (shared) in the assembly of Sun servers and workstations. The challenge was to compute procurement plans for components with long (~13 weeks) lead times to meet future demand for servers and workstations where the demand was described by a probability distribution. Fun, right? Today, Rapt would be positioned as a Data/AI/ML company. In 1998/99, the term Data Science hadn’t even been coined. Better yet, Spark didn’t exist. Neither did Hadoop. As usual, I digress.</p><p>Tom Chavez was one of the founders and the CEO of Rapt. At the time I found them on Accel’s website, the company didn’t have any other employees other than the founders — everyone else was a contractor. I wrote to Tom on a Wednesday afternoon, waxing eloquent about how my background in Math and CS would be perfect for the company, etc., etc. He responded on Thursday and asked me to come in for an interview on Sunday afternoon. Sunday afternoon found me at Rapt’s offices — a one-bedroom apartment in Potrero Hill that had been converted to an office where ½ of a wall was just stacked up with empty Pizza boxes and right across from the apartment was a tennis court in the apartment complex itself. And I thought to myself — pay dirt! Coding, pizza, and tennis — the perfect early-stage startup experience. I wanted this job!</p><p>I was interviewed by Tom and Adam Galper, co-founder and CTO. My interview lasted roughly 90 minutes and luckily for them (and me), Rapt was not using Microsoft COM. When the interview ended, Tom drove me to an alley called Ritch Street in SOMA and showed me Rapt’s new offices — in a small warehouse like building on 324 Ritch Street. My mind was racing with all sorts of questions — why is he showing me around the new offices, did I crack the interview and do I already have a job — I was confused. As I was trying to make sense of all this, Tom said, “look, I don’t know where you are in your job search but it’s clear to me that you have a lot of gumption when it comes to problem solving and early stage company building and I’d like you to come work with us at Rapt.” My first (internal) reaction was, “gumption? Really? People use GRE words in day to day conversations?” I did summon the good sense finally to express my gratitude for the offer and that I’d get back as soon as possible.</p><p>Along the way, I had interviewed with and also received offers from companies in Boston, Mountain View, and Denver. Somehow the idea of moving to Boston or Denver was more appealing before I started my job search than after I had concluded it. Ultimately, inertia won and I accepted the job offer from Rapt. So, what about luck and timing then? Well, I would later find out that the day I found Rapt on Accel’s website was the day after the portfolio page was updated to include Rapt and it was a week after Rapt had closed their Series A with Accel.</p><p>What luck! And timing! Yes, inertia and gumption helped too. I don’t know what would’ve happened had I not been on Accel’s website that day and found Rapt. What I do know is that I wouldn’t be where I am today were it not for the perfect alignment of the sun, moon, and the stars — otherwise known as luck — that began my partnership and friendship with Tom.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=952d32cd3282" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Humility, Grit, and Self Deprecation — MA110 @ IIT Delhi]]></title>
            <link>https://vsvaidya.medium.com/humility-grit-and-self-deprecation-ma110-iit-delhi-c943331b6956?source=rss-718d5493dd86------2</link>
            <guid isPermaLink="false">https://medium.com/p/c943331b6956</guid>
            <category><![CDATA[iit-delhi]]></category>
            <category><![CDATA[grit]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[humility]]></category>
            <dc:creator><![CDATA[Vivek Vaidya]]></dc:creator>
            <pubDate>Thu, 02 Jan 2020 22:24:18 GMT</pubDate>
            <atom:updated>2020-01-05T04:58:25.087Z</atom:updated>
            <content:encoded><![CDATA[<h3>Humility, Grit, and Self Deprecation — MA110 @ IIT Delhi</h3><p>Officially, the Silver Jubilee reunion for the IIT Delhi Class of ’95 ended on Saturday. But I wouldn’t get to go through the yearbook for the IIT Delhi Class of ’95 until Monday afternoon after a satisfying, delectable lunch of (leafy) Fenugreek cooked in a gram flour sauce seasoned with olive oil, mustard seeds and garlic — a Kumud Vaidya special — and hot chappatis, fresh off the stove. Ah, good old Maharashtrian comfort food. But I digress. The yearbook. Right. And to some “unforgettable moments at IITD”. I recounted some happy moments — football matches won, trips taken with mates, and general mischief and buffoonery that one might expect from, ahem, young adults. I was surprised to find out, that for some of my batch mates, MA110 was an unforgettable moment. Which made me realize, especially considering I’ve told this story multiple times to my son, Viplav, MA110 is right up there in my list of unforgettable moments at IIT Delhi too!</p><p>To understand why this was so, let’s rewind back to August/September 1991. Each course that we took at IIT Delhi had a code: 2 letters to indicate the subject and 3 numbers to indicate the course number within that subject, so MA110 was course number 110 in the Math (MA) department and CS101 was course number 101 in the Computer Science (CS) department. MA110 was, literally, the first course that we took at IIT Delhi — the syllabus was Advanced Calculus. At least. The operative word being Advanced. The recommended textbooks for the course were Calculus Volumes I and II by Piskunov and <a href="https://www.amazon.com/Advanced-Engineering-Mathematics-Erwin-Kreyszig/dp/0470458364">Advanced Engineering Mathematics</a> by Kreyszig. The Piskunov books aren’t published anymore. As you might expect, examinations were a big part of our life at IIT Delhi; after all, how else would you grade students and show them their place in the world? MA110 had 5 exams over the course of the year: 2 quizzes worth 10 points each, 2 minor exams worth 20 points each and 1 major exam worth 40 points.</p><p>Before we go any further, let’s pause for a moment and reflect on the fact that all the 300 odd students in that freshman class had cleared the most difficult examination in the world and were all used to being in top 3 to 5 students in their respective classes from Kindergarten all the way through high school. Not exactly a group that’s used to failure. Especially, academic failure. So, the results of the first quiz came as a big surprise to everyone. And that’s an understatement. The average score was 5/10. I got a 3 — thanks, Bewad! Needless to say, there were a lot of wounded egos walking around campus that day.</p><p>But that’s not what made MA110 unforgettable. It was the first minor exam that really showed us our place in the world. It was, as if, the professors were not done heaping misery, doom, self-doubt, and an overall sense of inferiority on us — if enough is good, too much is better, right? The average score for the first minor was 1.5/20. I got a 0. Yes, a zero! 83 students (28%) flunked that class and had to repeat it. And, to add insult to injury and to — what seemed at the time — mess with our minds, the final grades were posted for everyone to see on the penultimate day of the major exams. 83 students walked into the major exams for CY110 after having been told that they had flunked their first course at IIT. Go figure. I have never been prouder of a C in my entire life as a student as I was of the C I got in MA110.</p><p>Looking back, there were a lot of things I learnt from the MA110 episode that, with the benefit of hindsight, introspection, and yes, old age, I have been able to put in the right perspective. The top of that list is Humility. Many Megabytes (maybe Gigabytes, even, if you include the videos) have been written on the subject of Humility and Leadership — the tl;dr of all the literature on the subject being that to be a good leader one should get comfortable with not being the smartest person in the room; in fact, a good leader surrounds themselves with smart(er) people, learns from them and then depends on them to do what they do best. I consider myself extremely fortunate to have interacted with some wickedly smart people during my time at IIT Delhi; in fact, some of them are really good friends and all of them were and continue to be extremely generous with their time to teach and help me grow. Often times, though, humility is perceived to be a weakness. What I learnt via MA110 was to be fierce and humble. Fierce humility, if you will, achieved through resilience and grit.</p><p>Grit. Best exemplified by VVS Laxman and Rahul Dravid in <a href="https://en.wikipedia.org/wiki/Second_Test,_2000%E2%80%9301_Border%E2%80%93Gavaskar_Trophy">that</a> <a href="https://www.espncricinfo.com/series/15565/scorecard/63920/india-vs-australia-2nd-test-australia-tour-of-india-2000-01">test match</a>. To fail fast and shake it off. To never relent and to not quit. Inspirational words that sound appropriate in retrospect. Back then, I was just determined to not flunk that class. And, I worked very hard to get that C. Later on in life, there would be many instances in my professional life when things didn’t necessarily turn out the way we wanted, but through resilience and grit, we figured out and achieved the best possible outcome (our own version of a C, if you will) given the circumstances.</p><p>And finally, I learnt the value of humor and being positive in life. In adversity. Coming out of the examination room after the first minor, Rohit asked me how I had done and I replied, “I didn’t get a single question right. I am going to get a zero”. “No way. I bet you 10 rupees that you won’t get a zero”, he shot back. Of course, I won the bet. Little did I know that what I was telling myself that day was, in the words of Tom Chavez, my friend, business partner, and hetero life mate, “You can’t change the past. Today is the first day of the rest of your life. Focus on that.”</p><p>So, yeah. Thanks, MA110. Unforgettable!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c943331b6956" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>