<?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 Luv Jain on Medium]]></title>
        <description><![CDATA[Stories by Luv Jain on Medium]]></description>
        <link>https://medium.com/@luv.jain01?source=rss-c0db19ed816a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*O37LHYwji_Ydr5BK8e2BMg.jpeg</url>
            <title>Stories by Luv Jain on Medium</title>
            <link>https://medium.com/@luv.jain01?source=rss-c0db19ed816a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:04:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@luv.jain01/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[The Crud-ity of Data]]></title>
            <link>https://medium.com/codewithluv/data-d90dedebd096?source=rss-c0db19ed816a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d90dedebd096</guid>
            <dc:creator><![CDATA[Luv Jain]]></dc:creator>
            <pubDate>Tue, 15 Oct 2019 22:01:08 GMT</pubDate>
            <atom:updated>2019-10-17T00:05:06.374Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*2w2_3w8m_-sELQQwKwR6nQ.jpeg" /></figure><p>Hi, hello. It’s me, again.</p><p>I went on a date the other day, and I got told something that confused me. The girl said she couldn’t get a “read” on me. I don’t consider myself an enigma in any way, but that baffled me. What do people want to know about me? I’m beginning to believe that companies may have a better “read” on me than even I do of myself. What does that mean? Here I am, having a pretty intimate chat over Indian street food with a lovely woman and my smartphone is ready to suggest me to go get toilet paper at the store next door. That <em>terrifies </em>me.</p><p>If you haven’t noticed, I like these posts to be an open conversation. So, let’s converse. Why does this terrify me? Well, because there are entities on this world that know my exact habits to a tee. I’m not a repetitive person in the slightest, but when Google or Apple suggest that I need to get a new bottle of Dove post-shave moisturizer after I get a haircut, it makes me wonder if I am. Have we all really become that predictable that something that doesn’t breath can get a read on us to the point it can help? Ah, but wait, is it helping? I believe it’s offering help, but what’s the limit? When does this help become a form of marketing?</p><p>Let’s walk through this, step-by-step. Forgive the crud-ity but I’ll stick to toilet paper as an example (pun intended). I’m with my friends for a day and I mention that I need to do groceries and get toilet paper — as a joke (partly, post college life is hard, man). In this hypothetical world, Google is now trying to enter the toilet paper industry with their brand new optimization algorithm for ply-count (you get the idea). Now when my phone tells me there’s a Walmart close-by and I can get Google branded toilet paper, is that helping me? It is, but isn’t it also leading me to only get a certain brand of toilet paper? I may sound very tinfoil-hat like here but follow me through a more real world version where this can be implemented. Ever received a notification asking for a review on a certain place or about a certain type of food you’ve been talking about with people? That tells me that entities are able to combine our location with phrases it can capture from us and provide an output. Getting from that to just putting in a simple suggestion towards a product that is paying for advertising isn’t so hard.</p><p>You know what seems so innocent? Those little quizzes you find online about “Which Marvel hero are you?” or something. I opened one of those up the other day (spoiler alert, I am Iron Man). The first question it asked was about “what your favorite type of take out is”. I thought, okay, maybe these heroes have a take out order, interesting. Next question was “where do you like shopping”. Now hold up. These types of questions went on through about 30 more “next” button presses and by the end I realized I had just been played. In 35 odd questions, this quiz had just taken so much of my data and probably sent it to some advertising company that now knows where/when/how I like certain things. In return, I got told I was Iron Man.</p><p><em>Why?</em></p><p>In a great post describing how Machine learning works by <a href="https://medium.com/u/ba4c55e4aa3d">Adam Geitgey</a>, he writes: “As machine learning becomes more important in more industries, the difference between a good program and a bad program will be how much data you have to train your models”. He goes on to point out “that this is why companies like Google and Facebook need your data so badly!”. That’s great, I’m all for machine learning and progressing with technology. This got me curious though in regards to the data that has already been collected about me. I decided to do some investigation as to what my “read” is to Facebook and Google.</p><p>First Google, come at me Sergey. I personally subscribe to Google play music and have a wide variety of music preferences usually dependent on mood. I think like most people, my mood alternates throughout the day. I opened up my Google play playlists and looked at the songs that I liked and added to them. I have three main playlists:</p><p>Rise — Wake up, blood pumping stuff to get me ready for my exciting day (it always amuses me to bump Kanye when I’m writing code for a bank).</p><p>Chill — Deep beats for actually working and focusing.</p><p>Mood — Everything from old school Bollywood to modern hip hop.</p><p>Now the brilliant engineers over there, have actually attached a time and weather condition to all the music I’ve ever interacted with. They even track if I finished listening to the track or not. So, if it’s bright and Google knows it’s my shower time and my phone suggests me to listen to some Shakira, will I listen? Unfortunately, that’s the precise time when my hips don’t lie, so yes. But, do I really need that level of detail?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iEM5UaKcw0YASu91nUrfYw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*JSVWWuBIQ3F01gFxGnXg6w.png" /></figure><p>Alright, let’s do this, Zuck. This honestly made me sad. Here’s one of my favorite pictures of my brother and I at Mt. Rainier over a summer, during a surprise visit. This picture holds so many special memories and always makes me smile. And below are the tags that Facebook has decided to mark this as. “people smiling, sky, cloud, outdoor and nature”. Now I love computers, I’m a techie at heart. But, this is sad. Such a special memory and one of the only permanent labels that this will go down having is “people smiling”. Maybe it’s a good thing, that it’s not able to process all the emotion behind the picture.</p><p>How to do this: Go to any picture on facebook, right click -&gt; inspect</p><p>But why is this being done at all? If any artist decided to pay Google or Facebook to advertise their track for a “person smiling in outdoors” to listen to their new soundtrack about that, is it because I would like it or because there was money transferred? What model is being trained and how is it going to affect me? Can we imagine a world where there are deeper tags on the picture like “proudly smiling, surprise, bliss”? More importantly, are we ready for that world?</p><p>I’m not. But hell, maybe this will go well for dates in the future. I can hand over a little text document telling her all the tags that Facebook and Google have me as. After all, who has the better read on me at that point ;</p><p>Me or the data?</p><p>Hi! I don’t like to end these blurbs without saying thank you to the people who talk data with me, that’s all of you. But especially you, thanks for conversing with me.</p><p>If you’re new, hi! Here’s my first post to find out who I am: <a href="https://medium.com/codewithluv/hello-world-ae68a165eb4b">Here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d90dedebd096" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codewithluv/data-d90dedebd096">The Crud-ity of Data</a> was originally published in <a href="https://medium.com/codewithluv">CodeWithLuv</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customer Obsession]]></title>
            <link>https://medium.com/codewithluv/customer-obsession-1742f647ee23?source=rss-c0db19ed816a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1742f647ee23</guid>
            <dc:creator><![CDATA[Luv Jain]]></dc:creator>
            <pubDate>Mon, 24 Jun 2019 01:34:11 GMT</pubDate>
            <atom:updated>2019-06-24T01:34:11.878Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uF1L-NGa6YswJs9LqVA7bQ.png" /></figure><p>Welcome back! Now that we’re done with introductions (if you haven’t read my first story: <a href="http:// https://link.medium.com/N73NYVwEaX">Here</a>!) — I feel it was important to give some background on who I am and why I’m here. This story will be all focused on the Amazonian principle: “Customer Obsession.” I thought it would be really cool if I, as well as a bunch of other current and ex-Amazonians, comment on the principle and what it means to us. Then, to wrap it up, I’ll give my own analysis on how it should be used. Before we do that, I think the most important question begs to be asked.</p><p><strong><em>What is Customer Obsession?</em></strong></p><p>Customer Obsession is the number 1 principle out of the 14 principles that guide Amazon and our holy father, Jeff Bezos. The description is as follows:</p><blockquote>Leaders start with the customer and work backwards. They work vigorously to earn and keep customer trust. Although leaders pay attention to competitors, they obsess over customers.</blockquote><p>Now, before I give my own thoughts, I reached out to a couple of people (Remember, I said I know the coolest folks) to talk about their own interpretation about this principle and I’d like to attach their views.</p><p>Everyone, meet Austin. Austin, everyone.<br>Austin is my dear friend from UCLA and is a Computer Science graduate. I met him during my time at Amazon and he’s a current Software Development Engineer there doing amazing work. My man, Give me your thoughts on Customer obsession!</p><p><a href="https://medium.com/u/7680eb8d454c">Austin Vaday</a>: Customer obsession? Ah, the principle we abide by day and night. Everything we do, every small action we take, is for the customer. It seems easy, right? Alas, not so fast. Something I personally learned while working at Amazon for these past 3 years of my life is that there’s never just one customer. I’m not talking about the myriad people purchasing or using your product. Nope, I’m talking about this from an engineering perspective. As an engineer, my end-users are my customers, sure, but my co-workers are also my customer. My manager, my program managers (PMs), my UI/UX designer, and my stakeholders are my customers as well. Everything I build is for these folks that I work with, just as much as it is for the people that end up using the product. And truth be told, there’s no way you can make all of these customers happy. In the end, it’s all a balancing act. If my fellow engineers want something implemented in a different way, I’ll see what I can do. If my manager needs a certain feature completed in a certain period of time, I’ll see what I can do. If my UI/UX designer wants a slightly different front-end layout for experimentation purposes, I’ll see what I can do. Indeed it’s a balancing act of negotiation, a world series of never-ending trade-offs that need to be made day and night. It’s about prioritizing what your customers need — and working towards a solution with the capacity you have at hand. A customer obsessed mindset allows us to thrive as individuals striving to provide one simple thing for the world: an amazing product.</p><p>(He showed customer obsession by writing that).</p><p>I personally believe that there are so many ways to interpret Amazon’s principle and assign meaning (there are actually books on this stuff), but the first sentence itself says everything to me : <em>Leaders start with the customer and work backwards.</em> I see that there’s almost a fear that keeps companies and leaders from obsessing about their customers. The current strategy seems to be just paying attention to the latest technology fad and what the market sizes say and building technology around that. Truly, that isn’t so bad, working with the latest tech, you’ll have chances at having a good product. But wait, <em>isn’t a product meant to be for the customers</em>? It’s not supposed to appease to some Ex Machina type figure. I personally feel working backwards from the customer will always deliver the best product. You’re strategizing an entire product and in some cases, an entire company around what you’re providing to the customer. Why not build it, obsessing over what <em>they</em> want? Given that, it makes sense to me that software should be built starting from the customer. It’s such a crucial step on how to build an entire enterprise, that when done correctly, you can get a company that can shatter the industry. Now just to be clear, this is not to say that the customer is always right (Slow your beans, Karen, you cannot speak to the manager) but it’s important to earn and keep absolute trust.</p><p>The concept is simple if you really begin to think about it. You focus all your research onto finding the exact customer need. Then you utilize <em>everything</em> to invest in the right tools, people, and skill-learning to meet that need. The way I see it, building a product that truly is built from the customer needs will handle marketing, publicity, and even profitability on its own. It goes back to supply vs demand on a very fundamental level, almost.</p><p>Let me try breaking down an example. Just play along because we’re about to get wild. Let’s say that around this exact time, there’s a company building a new phone. Now to add some spice, you and I both know that right now Virtual Reality or, VR is one of the hottest tech buzzwords. This company starts thinking oh, we should build a camera on the phone that takes VR/AR photos to combat Google’s playground camera (which is dope, by the way, I’d recommend checking it out). But wait, the company’s customers, you and I, want to take selfies. Wouldn’t it be more important to perhaps look into a better way to engineer front-facing camera quality? Make the quality of the camera and the software processing it top notch, and you have yourself a product that is addictive and beats the market. Now while customer obsession absolutely entails building the product with cool features, it also involves customer support, suggestions, returns, retention, etc.</p><p>Now, this becomes so much cooler when you yourself are the customer. Imagine building a product that you’d want to use. You, yourself can then start asking “How would I want this?” or “What features would I love to see in this?” I think my favorite time when I saw this “self-obsession” (heh get it, self is the customer) was during my final semester in college. My family lived in Cleveland and my school was in Columbus (That’s like a 2 hour drive through farmland). I was home for the weekend and was heading back in the middle of winter so I looked up the weather in Columbus and it said sunny. Great, it was sunny in Cleveland as well. When I started driving, an hour in I get hit with quite possibly the worst snowstorm I’ve ever seen. This single incident is how I started to think about my main side project I’m doing to this date. It hit me that you can never know the weather along a route until you get there. I wanted to dive in and build something that could fix that. I wanted to get into what features I would personally love and how could I best support myself. (Know thyself, right?). What was truly obsessive though was how I bugged my friends on what they’d want the application to deliver. I knew that many of them suffered the same problem I did and understanding what their view of a solution looked like led me to some of the best ideas.</p><p>Most people would look at my situation and just think to check multiple check-points. From what I saw, a consumer who faces the problem builds the best product. I say this because a consumer who actually understands what the challenge is that they’re dealing with will have the best ideas on how to avoid the issue. I think given any person in that situation, each would have their own creative way of getting out of the issue. That’s almost talking about humanity on a primitive level; put a person in a problem and watch them problem solve. Now, if you’re an obsessive problem solver, such as myself and you throw in some basic programming knowledge, you start to think about a <em>world in code</em>. More on that later, but I can confidently say that the best producer of a product is one who’s a customer themself.</p><p>What I think is especially beautiful about this, is that the solution is built by the customer, for the customer. And isn’t that what a product should be in the end? Huh, it’s like if you are the customer and you start building products and software that you, yourself would use, you’d be setting yourself up for success. Don’t believe me? Take Facebook, Amazon, Google, Apple, Uber, and Airbnb.</p><p>I’ll wait.</p><p>And for all my readers and supporters, I thank you. You all are my favorite customers and I enjoy obsessing and taking feedback from all of you, but especially you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1742f647ee23" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codewithluv/customer-obsession-1742f647ee23">Customer Obsession</a> was originally published in <a href="https://medium.com/codewithluv">CodeWithLuv</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello, World!]]></title>
            <link>https://medium.com/codewithluv/hello-world-ae68a165eb4b?source=rss-c0db19ed816a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae68a165eb4b</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[musings]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Luv Jain]]></dc:creator>
            <pubDate>Sat, 01 Jun 2019 17:16:51 GMT</pubDate>
            <atom:updated>2019-06-01T17:16:51.963Z</atom:updated>
            <content:encoded><![CDATA[<p>So, I’ll start off by being honest. I never thought I would go into Computer Science ; I really didn’t. Sure, I was a nerdy kid. I would sit in the car with my dad for long road trips and discuss time travel, and ask him his thoughts about parallel universes. As a kid, that kind of stuff was awesome to me. (Hell, it still is). The possibility, the potential, the <em>freedom</em>. But code? Seeing my dad, back when he was a dev, I saw the deadlines, the panic, the constraints. I never understood how a person like me could fit within a world of code. I knew that I dreamt to be free and maybe even explore the universe. I wish I could write that when I started to actually write code, I woke up from that dream. I did, but I still wasn’t grounded.</p><p><em>Coding let me fly.</em></p><p>It was addicting. The words appearing on the screen, the calculations being done, the way everything just <em>worked</em>. As most software engineers do today, I started out with Java in a computer science class. I’m still ashamed to say this, but I was terrible. I tried so hard to understand syntax, and when I finally got it, I then didn’t understand object oriented design. That whole dance baffled me for the better part of a few months, but sure as the sun, I saw the potential in it. I immediately found that I started thinking about the entire world around me as code. It still happens and I like to think it’s what keeps it magical to me, still. Everything is a problem itching to be solved by any combination of creativity and logic.</p><p>I know what you’re thinking.<em> This kid needs to grow up</em>. Lucky for you, dream-killing reader, I went to college. Now, while my view didn’t dissolve, it did evolve. Throughout my time at college ( OH! ), I had a lot of interactions where I’d like to think I got to use my logical problem-solving skills. However, those were all pre-planned assignments. For me, a problem that’s been solved before takes away an aspect of creativity. That being said, I was lucky enough to do a couple of internships and I’d like to think they taught me some really cool things. These were my first tastes of the real world where I got to bring in everything I had to solve problems and all were invaluable experiences. I’ll do a brief summary of each of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/1*wWzTyfPy4B-iADiSKBaxLA.png" /></figure><p>My first internship. Can you believe I used VB.net? I was a Quality Assurance engineering intern and yes, it sounds terrible. However, undeniably, I would recommend everyone to start their own software journey with testing. Testing truly lets you see why the code was built and how it was built. When you actually probe into what the code is doing, part of you hopes it breaks, part of you hopes that it works. It was fun to make the code break (Yes, looking back at that sentence when I unit test makes me feel like an idiot). While I may talk about and praise testing, the real lesson I got from my time at Snap-On was that creativity is the greatest tool an engineer has. For those who don’t know, part of Snap-On involves managing the catalogs that you see in a car dealership with all the parts for vehicles. I was tasked to perform stopwatch testing, and was actually handed a physical stopwatch and told to time results for the parts catalog on the most clicked on objects, which were given on an excel sheet. ( I know, I know). I was in shock. I realized I could absolutely just go with this approach and please my boss. But, something was knocking. That inherent creativity was just begging to come out. What I ended up doing was building a graphical user interface (gui) around the catalog — so then it’s actually possible to interact with those elements automatically and having a script to click through every single possible element and record the times on its own on an excel sheet. (Sue me, I couldn’t change everything). The true joy of software development came to me when I saw the potential in code. This led to the understanding that anything can be done — that’s pure magic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*Mshoz-gNcrgKKMvUMvroYg.png" /></figure><p>JP Morgan was the first time I felt I actually experienced the software lifecycle. It was a breath of fresh air to come out of the regiment of programming assignments into a world where I could actually deliver real code. Or so I thought. However, it did lead to a very important skill I believe every person in this industry needs to know. How to truly collaborate within software. I wish I could say JPMC was open source, or at the very least, just taught git. That would’ve taken collaboration to another level, and saved lots of headaches in the future. However, this was more in the sense of working with multiple people and trying to understand everyone’s opinions and making them alive within code. I was assigned with building a dual data synchronization service for the Forbes Billionaires clients. ( Yeah, I’m kind of a badass). This was essentially so these wealthy clients’ bankers could keep track of the billionaires’ assets all over the world. Basically what I built was a service that whenever someone like Bill Gates bought a timeshare in China, his asset manager would able to tell him, hey buddy — slow the roll you just bought something in China, let’s not invest just yet in that condo in Maui. Immediately, my mentor told me one way to build it, my fellow intern another, and I had another way. While tensions easily became heated due to a lack of understanding, it was relieving to build a common solution to solve problems together. It thrilled me to take one person’s thought process and another’s and another’s (then ultimately taking your boss’) and combining them together to build a wonderful solution. I look back at JPMC and think that I didn’t learn too much software management, but I did learn people management within software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*F66ctDBuIkkPnCKImUa4ag.jpeg" /></figure><p>I was here for two summers, and regardless of how it ended — they were the best two summers of my life. Here, all of my software skills were truly put to the test, and while I sometimes felt like the stupidest person in the room, I loved it. My first summer was on the Shipping Platform Tools team and when I was invited to return the next summer, I joined the Alexa Machine Learning. Amazon has a core principle at the heart of the entire company that is the most important lesson I’ve learned in software development. I’m proud to say that I have taken this and applied it to everything I do in my work. Customer Obsession. I’ll do another blog post about it (Future Luv will put the link here), because it deserves it. Both my projects, while tough, allowed me to flex my software muscles as hard as I could and I will always admire Amazon on a very deep level for that. I was able to learn something new every day and that curiosity, hunger, and drive continuously flourished. And that flourishing will probably be one of the most beautiful times.</p><p>So you’re probably asking yourself (All my friends who proofread asked this, so don’t lie) : Alright Luv, that’s dope and all. What’s your point with this blog? Why make this story? Who’s this for? The entire point of this blog is whatever you, the reader, want it to be. Whether you’re a recruiter and want to talk about potential job opportunities and are scouting me out, a friend trying to find funny evidence of me on the internet (Screw you, Kevin), or a curious person wanting my insight on software dev, I’m here. I’ll be writing stories here about my personal views on things I notice in software engineering companies, my own musings within general tech, and even featuring interviews with cool folks I know. I think this blog will flow best when it’s about my own interactions without revealing any dirty laundry. (I’m not even going to pretend, those last two sentences were entirely my dad’s words. You the bomb.com, father). Now, I’m at Capital One working on some pretty cool product-facing teams and trying everyday to use these previous lessons in my work. I’m just here to show you guys I know what I’m doing (kinda). I guess this is me, putting the Luv in CodeWithLuv.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*LRhj4C9bKyAN33xfCca3fw.gif" /></figure><p>Welcome, and Hello, World.</p><blockquote><em>Programming is like brushstrokes on an easel. With the right movements, you can create anything your mind conjures.</em></blockquote><p>Before I let you go, it wouldn’t be fair to end this first post without giving a proper shout-out to my team. All of my friends who have given me nitpicky comments, grammar catches (I’m sure there’s still a few), and just the courage to write this first post ; from the bottom of my heart, Thank You.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae68a165eb4b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codewithluv/hello-world-ae68a165eb4b">Hello, World!</a> was originally published in <a href="https://medium.com/codewithluv">CodeWithLuv</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>