<?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 Pia Chakrabarti on Medium]]></title>
        <description><![CDATA[Stories by Pia Chakrabarti on Medium]]></description>
        <link>https://medium.com/@piachakra?source=rss-168d9f8af01f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lHphjRx315IRX-Io.jpeg</url>
            <title>Stories by Pia Chakrabarti on Medium</title>
            <link>https://medium.com/@piachakra?source=rss-168d9f8af01f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:18:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@piachakra/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[Picking A Domain Name For Your Startup]]></title>
            <link>https://medium.com/@piachakra/picking-a-domain-name-for-your-startup-e38ce0a2e977?source=rss-168d9f8af01f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e38ce0a2e977</guid>
            <dc:creator><![CDATA[Pia Chakrabarti]]></dc:creator>
            <pubDate>Tue, 04 Mar 2014 00:16:59 GMT</pubDate>
            <atom:updated>2014-03-04T00:16:59.234Z</atom:updated>
            <content:encoded><![CDATA[<h4>Oh, the lack of possibilities!</h4><p>When I was working at White Shark, we spent many sleepless nights in the common room blurting out random string of words, then pulling out our hair realizing that everything in the world.com was taken! Unfortunately, there are only a few work arounds for this dilemma.</p><p>1) Misspell a word. I call this “being cute”. Many companies have done this. Replaced C’s with K’s, dropped or added vowels, etc. My personal school of thought on this is that do I want my product to be spelled in a baby talky way? No. And most importantly, it would be annoying to spell it out over and over again to new people, especially in loud settings which is often where I find myself talking up new apps and tech things.</p><p>2) Forget about .com. Initially, the team did not want to go for a . anything else because for some odd reason we all feel this false sense of security with .coms. But we are going to have to let go and give in to the .co, .ly, .io, etc. if we want to keep the integrity of the name/spelling. I don’t think that a website has to have a .com on the end anymore to be taken seriously. I wish we had given up on .coms from the get go because there are so many more options if you do.</p><p>As for brainstorming names, we jotted down words (literal/figurative/feeling inducing) to describe our product on a whiteboard and added to the list whenever one of us had a thought. Our top resource for creating the domain name was domize.com, which shows you whether the .com/.co/.net/.org/.io are available for the name you want. There are also a variety of domain name generators out there which will help you combine words or give you more ideas based on words you provide, but I felt that random combined words didn’t have the.. weight or meaning we were looking for. Luckily at some point the team decided on a name and I think it’s perfect!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e38ce0a2e977" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Building Software, Less is More]]></title>
            <link>https://medium.com/@piachakra/when-building-software-less-is-more-67cf5279fd73?source=rss-168d9f8af01f------2</link>
            <guid isPermaLink="false">https://medium.com/p/67cf5279fd73</guid>
            <dc:creator><![CDATA[Pia Chakrabarti]]></dc:creator>
            <pubDate>Tue, 03 Dec 2013 16:36:03 GMT</pubDate>
            <atom:updated>2013-12-03T16:36:03.670Z</atom:updated>
            <content:encoded><![CDATA[<p>This may come as a surprise — people don’t deal well with options, yet I am obsessed with them. Before buying something or traveling somewhere I go into “obsessive research mode”, which for some reason is fun for me. I once went to a sari shop in Kolkata and I kept insisting that I needed to see all of the saris before I make a decision. I had already picked a few that I liked but I was afraid of missing “the one”, the classiest/sexiest/most beautiful sari of them all. About fifteen saris in, the store owner tells me</p><blockquote><em>“Sorry mam, I can’t show you any more saris. It will only confuse you.”</em></blockquote><p>Similarly, although we think that the more customization options we offer, the more the user will enjoy using our software, the truth is that too many options overload the user. Before adding an option, evaluate how likely it is that the particular option will be used. For example, would a user find it an absolute necessity to be able to choose the font of their dashboard landing page? No. That adds more work for the user and takes away from the intended purpose of the software. As someone building the software, you must have faith that <strong>you </strong>know best and are qualified to make many choices on behalf of the user. Fortunately, software, particularly online platforms, can be tweaked and redeployed easily so even if you do end up making a bad decision once in a while, it’s not the end all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67cf5279fd73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working in a Startup House]]></title>
            <link>https://medium.com/i-m-h-o/working-in-a-startup-house-1562776e7291?source=rss-168d9f8af01f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1562776e7291</guid>
            <dc:creator><![CDATA[Pia Chakrabarti]]></dc:creator>
            <pubDate>Mon, 25 Nov 2013 15:32:19 GMT</pubDate>
            <atom:updated>2013-11-25T15:32:19.566Z</atom:updated>
            <content:encoded><![CDATA[<p>I never thought I would agree to move in with 3 strangers who I had never met in person in a city across the world, where I knew almost no one. But when I was given the opportunity to work with a few talented guys in a startup house in Mumbai, India, I said yes, and I’m glad I did. I think working in a startup house is ideal for a very small company (around 5 people), particularly in the inception stage of a product.</p><p>1. <strong>No need for formal meetings. </strong>Within the software community it is a growing belief that traditional meetings are useless. Many companies are making use of daily scrums, which calls for brief 15 minute meetings at the same place, same time, in the morning. Everyone on the team is required to attend and at my previous workplace, everyone was required to stand during the meeting. At a startup house, I don’t think a daily scrum is even necessary. We are together almost all the time and can discuss issues as they arise. No need for agendas, powerpoints, technical difficulties with the projector, and black coffee to stay awake through all the nonsense. We often find ourselves brainstorming while just lazying around the house together.Collaboration just feels organic.</p><p>2. <strong>Flexibility in work hours. </strong>I am not a morning person. Please don’t talk to me before 10am. Don’t even look at me. At the startup house, I’m able to start and stop work on my own time. Although we overlap a lot, I feel we are sometimes more productive because of different schedules. For example, after I am done testing, updating the defect tracker, and heading to bed, the developer is waking up from a nap and getting ready to program. By the time I’d wake up again, many of the issues of last night would be resolved.</p><p>3. <strong>It’s the ultimate exercise in “team building”. </strong>If you are working at a small startup, clearly you are passionate about what you are doing and you should be passionate about the people who you are on this journey with. If you are the type of person who finds it hard to get along with others, startups are not for you. If you do like your coworkers, spending time with them does not seem like a chore. By living with your coworkers you learn what their strengths are and where they need help, where you could possibly step in. You also learn a lot from your coworkers, since the skills and experiences of the team members vary from one of another.</p><p>Living with your coworkers is not very different from living with any random group of people. To make it work, everyone has to respect each other’s time and space. If you are an easygoing person who doesn’t find it difficult to adapt and are looking to dedicate a lot of time to a particular product/cause, I recommend trying out a startup house. Disagreements will happen and awkward situations will occur. Hopefully you can laugh it off and chalk it up as a fun story to be told one day in the distant future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1562776e7291" width="1" height="1" alt=""><hr><p><a href="https://medium.com/i-m-h-o/working-in-a-startup-house-1562776e7291">Working in a Startup House</a> was originally published in <a href="https://medium.com/i-m-h-o">I. M. H. O.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s Your Story?]]></title>
            <link>https://medium.com/i-m-h-o/whats-your-story-7104ca65a5d6?source=rss-168d9f8af01f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7104ca65a5d6</guid>
            <dc:creator><![CDATA[Pia Chakrabarti]]></dc:creator>
            <pubDate>Fri, 15 Nov 2013 18:08:09 GMT</pubDate>
            <atom:updated>2014-01-08T05:35:55.272Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been blogging for over 10 years, mostly about random things that may not pique anyone’s interest but my own. So I decided I want to start a blog about my professional life, in hopes that what I write will help someone like myself, someone who is looking for answers. To begin with, I should tell you my story. My parents immigrated to the United States in 1981 from India, and I was born approximately half a decade after. I was raised in America, but I connect on many levels with Indian culture. I think being an Indian American to a degree, shaped my decision of choosing a career in technology. Generally speaking, Asian families encourage their children to perform in STEM related subjects in school. Growing up, it was a given that my brother and I would follow in our father’s footsteps and become engineers. And so we did, sort of. I played around with several different engineering majors in college (and hated all of them) but decided upon Computer Science (which I actually enjoyed). I no longer write code, but I do work in technology and I love it. I spent the last 3 years working for a large corporation, consulting for the Public Sector in Washington DC and recently I decided to take a sabbatical to explore other opportunities in an effort to calm the “quarter life crisis syndrome”. Currently, I am involved at a startup in Mumbai, India and am also working at a technology consultancy NGO here. I would like to write about my experiences and lessons learned on this blog. Enjoy!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7104ca65a5d6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/i-m-h-o/whats-your-story-7104ca65a5d6">What’s Your Story?</a> was originally published in <a href="https://medium.com/i-m-h-o">I. M. H. O.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>