<?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[reflog - Medium]]></title>
        <description><![CDATA[reflog is a collection of essays written by Sanket on startups, company building, and life in general. - Medium]]></description>
        <link>https://medium.com/sanket-saurav?source=rss----8b6b51da28b5---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>reflog - Medium</title>
            <link>https://medium.com/sanket-saurav?source=rss----8b6b51da28b5---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:47:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/sanket-saurav" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to build magical products]]></title>
            <link>https://medium.com/sanket-saurav/how-to-build-magical-products-a3a2b866b1ca?source=rss----8b6b51da28b5---4</link>
            <guid isPermaLink="false">https://medium.com/p/a3a2b866b1ca</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Sanket Saurav]]></dc:creator>
            <pubDate>Fri, 26 Mar 2021 19:04:08 GMT</pubDate>
            <atom:updated>2021-03-26T19:06:46.275Z</atom:updated>
            <content:encoded><![CDATA[<h4>A guide to delightful product design with magic tricks.</h4><p>As the founder of a growing startup, I use an unusually high number of software products every day. Some of these products are critical to running our business, while others make me more productive. But out of all these products, there are only a few that I <em>absolutely love</em> using, even if they are more expensive than their alternatives — as compared to others that I wouldn’t mind replacing with a better, cheaper substitute.</p><p>So I tried to answer what makes the products I absolutely love different from the others that I still use but don’t care about a lot. I realized that all the products in the first category invariably have some bit of <em>magic</em>, while the others, remarkably, didn’t have any.</p><p>This post will explore what makes a product magical and replicate it in a product you are building yourself.</p><h3>Anatomy of a magic trick</h3><p>To understand what characterizes a magical product, let’s first define what <em>magic </em>is. This will help us put a framework on how we can think about our product.</p><p>Let’s take the example of the <em>Hat-trick</em>. It’s one of the most simple, classical magic tricks where the magician produces an object (traditionally a rabbit or a bouquet) out of an apparently empty top hat. What is the essence of this trick that makes it magical?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kv30iGwe6uUYA1yI1yGexw.png" /></figure><p>When you’re sitting in the crowd, and the magician performs this trick in front of you. The magician pulls a rabbit out of their hat. Assuming that you already don’t know how this trick <em>works</em>, since, well, it’s not really <em>magic</em>, you are amazed. <em>“Whoa! How did that happen?!”</em></p><p>The essence of this magic trick is the following two parts:</p><ul><li><strong>Preconception: </strong>When you came into the theater, your existing knowledge that you came in with didn’t allow for a rabbit to be pulled out of an arbitrary hat. That’s not how Physics works, after all. Reality doesn’t allow for objects to appear out of thin air. You’ve learned this from living your life in the real world so far.</li><li><strong>Stupefaction:</strong> At the beginning of the magic trick, you probably didn’t expect this to happen, assuming this is the first time you’re watching the trick. The magician didn’t announce that they are going to pull a rabbit out of the hat. They just did it.</li></ul><p>If the above two properties — preconception and stupefaction, don’t hold valid for the trick, it won’t be a magic trick anymore.</p><h3>Magical products you’ve already seen</h3><p>A computer mouse! Yes, people like you and me who <em>grew up</em> with the mouse as the primary way of interacting with a computer probably never thought of the mouse as <em>magical</em>. But <a href="https://www.theverge.com/apple/2011/11/2/2533794/andy-warhol-steve-jobs-apple-mac-paint">Andy Warhol</a> did. The first time that the famous pop art icon used the mouse in the paint program on one of the first Macs, he exclaimed, “I drew a circle!”. Magical, don’t you think? Preconception, as in Andy didn’t imagine something like that was possible in the physical world — and stupefaction when he could use something like that to create an actual circle on the screen.</p><p>I’ll take another example that’s easy to relate to. Superhuman, the popular email client. The first time I used the <em>Send later</em> feature, it was magical.</p><p>Preconception: I didn’t imagine that the software would interpret saying “<em>tomorrow 10am in san francisco</em>” correctly.</p><p>Stupefaction: It actually worked!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*SLW_LBWYc1TJWroIgF7JJQ.gif" /><figcaption>Superhuman’s “Send later” feature feels <em>magical.</em></figcaption></figure><h3>A recipe for magic</h3><p>Magical product experiences, as opposed to purely aesthetic design mumbo-jumbo, don’t just delight users. They also <em>simplify</em> the product for them. This is worthy enough to chase because users prefer simple products that just work rather than complex products.</p><p>So, how do we build magical product experiences anyway?</p><h4>Start at the destination</h4><p>When thinking about a new product feature, set aside technological constraints for a moment and first think about what the <em>ideal </em>end state looks like for the user. If you leave aside any technological constraints and solely focus on this, you’d end up with what your magic trick achieves.</p><p><em>The rabbit should appear from the hat.</em></p><p>In Superhuman’s example, the <em>Send later</em> feature&#39;s final destination is that the software should correctly guess the time in the correct timezone that the email should be sent at.</p><p>If you’re able to establish the destination well, you will fulfill stupefaction — the second part of our magic trick. The user will probably not expect this outcome from the product, even if they have a fair idea of the end goal.</p><h4>Map the shortest path to the destination</h4><p>Once the destination has been clearly defined, think about guiding the user to that destination via a path of least cognitive effort.</p><p>If a rabbit has to appear from the hat, the easiest way of making that happen is to, well, pull the rabbit out of the hat. The simplest way for the user to tell the software what time the email should be scheduled is to write it in plain English. What makes the <em>Send later </em>experience magical is that the user can write in half-complete phrases, and still, the software guesses the precise time and the timezone.</p><p>Conversely, think about a dropdown menu next to the text box to choose the timezone. While the destination is the same, the experience isn’t magical at all. The path to the destination is too complex.</p><p><em>Simplicity is magical.</em></p><h4>Put in the work</h4><p>Beware, for we’re talking about simplicity for the user — and not for implementation, which would invariably be more complex than usual if you’re optimizing for simplicity for the user.</p><p>A magical product experience simplifies things for the user but makes the technological implementation more complex by multiple orders of magnitude. A text box and dropdown would take far less time to implement than a full-blown natural-language processing engine that parses <em>“tomorrow at 10am in san fran”</em> to the correct time in the correct timezone based on the city’s name. (<a href="https://xkcd.com/1425/">obligatory XKCD</a>)</p><h4>Further reading</h4><ol><li><a href="https://www.toptal.com/designers/product-design/anticipatory-design-how-to-create-magical-user-experiences">Anticipatory Design: How to Create Magical User Experiences</a></li><li><a href="https://www.fastcompany.com/3045039/the-next-big-thing-in-design-fewer-choices">The Next Big Thing In Design? Less Choice</a></li><li><a href="https://uxdesign.cc/what-magic-can-teach-you-about-interaction-design-857ab052d1d8">What magic can teach you about interaction design</a></li></ol><p><em>Follow me </em><a href="https://twitter.com/sanketsaurav"><em>@sanketsaurav</em></a><em> and send me feedback or thoughts about this essay.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3a2b866b1ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sanket-saurav/how-to-build-magical-products-a3a2b866b1ca">How to build magical products</a> was originally published in <a href="https://medium.com/sanket-saurav">reflog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Why haven’t you hired more people in 2 years?”]]></title>
            <link>https://medium.com/sanket-saurav/why-havent-you-hired-more-people-in-2-years-e45b5a24b84?source=rss----8b6b51da28b5---4</link>
            <guid isPermaLink="false">https://medium.com/p/e45b5a24b84</guid>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[company-building]]></category>
            <dc:creator><![CDATA[Sanket Saurav]]></dc:creator>
            <pubDate>Fri, 11 Dec 2020 17:35:32 GMT</pubDate>
            <atom:updated>2020-12-11T17:39:57.202Z</atom:updated>
            <content:encoded><![CDATA[<h4>What making a ton of bad hiring mistakes has taught me about building teams.</h4><p>We’ve been screening several candidates for <a href="http://deepsource.io/jobs">a bunch of different positions</a> at DeepSource, and a particularly impressive candidate asked me during our conversation, <em>“It’s been 2 years since you started the company, but there are only 18 people. Why haven’t you hired more people in 2 years?”.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UbA4YxevKT-m1YV5nUOIbA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@quinoal?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Quino Al</a> on <a href="https://unsplash.com/s/photos/team?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I love it when potential hires ask me such thoughtful questions. It gives me a peek into how<em> </em>they evaluate a new job opportunity, especially with an early-stage startup. It also allows me to tell them more about my own thinking and explain the company’s mission slightly better. Questions about hiring are my favorite because it involves a certain kind of meta-thinking when you’re having this conversation in the hiring process.</p><h3>Post-mortem of a bad hire</h3><p>My co-founder and I have made our fair share of hiring mistakes in the past six years of our startup life, including, for the most part, the first startup which I had started right after college. Every time we’ve had to let someone go, we’ve sat down and introspected <em>why </em>we had to come to that stage. I am a strong believer in the notion that there are no bad employees, only bad hiring managers. So if I’ve had to let someone go, it was because of my fault and mine alone. Obviously, there are exceptions to this rule, but you know what I mean.</p><p>We concluded that most of the bad hires we’d made fell into one of these buckets.</p><ol><li><strong>They were hired out of desperation. </strong>We had bitten off more than what we could chew and got overwhelmed with deadlines, which led us to conclude that we need more people, and we need them soon. So we said yes to hiring without too much diligence or everyone saying a strong yes for them.</li><li><strong>They were hired for something that we hadn’t figured out how to do ourselves first. </strong>There was a pattern for this one and something that we repeatedly did. As tech founders, marketing and sales didn’t come naturally to us. It was easy to think that this <a href="https://sanketsaurav.com/the-messiah-hire-fallacy-325b663f2691">one person</a> can come in and do things magically. Well, guess what? It rarely works.</li><li><strong>Hired without having a repeatable process in place. </strong>This is a corollary to the previous point. But even if you’ve figured out how to do something, it isn’t easy for a new hire to perform well if you haven’t systemized the process.</li></ol><h3>Our hiring principles</h3><p>If you think hiring is difficult, try asking someone to leave.</p><p>We realized that the best way to optimize for good hires, especially in the early stages of a startup, is to hire deliberately. Of course, there would be situations when you can’t afford this — but beware that it comes with a trade-off of the possibilities of making a bad hire being greater.</p><p>We’ve come to put some principles in place that help us we’re not making the same mistakes again:</p><ol><li>Hire only after writing the exact job description and getting it reviewed internally.</li><li>Don’t hire for a position if you expect them to deliver or take accountability for critical projects or KPIs within 3 months from joining.</li><li>All of the founders should be on the hiring panel. So should at least 2 team members they are supposed to work with, in addition to the person they’d be reporting directly to.</li><li>Only hire someone when there’s a strong yes from everyone on the hiring panel. No exceptions.</li><li>Trust your gut.</li></ol><p>These are some very general principles that would apply to all early-stage startups — with some exceptions, of course. As more people get involved in your team’s hiring process, it is worth reiterating to them these principles. After all, <a href="https://en.wikipedia.org/wiki/Zen_of_Python#:~:text=Explicit%20is%20better%20than%20implicit,Flat%20is%20better%20than%20nested.">explicit is better than implicit</a>. Hiring is too important to be left to individual preferences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e45b5a24b84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sanket-saurav/why-havent-you-hired-more-people-in-2-years-e45b5a24b84">“Why haven’t you hired more people in 2 years?”</a> was originally published in <a href="https://medium.com/sanket-saurav">reflog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitHub Free and what it means for developer tooling companies]]></title>
            <link>https://medium.com/sanket-saurav/github-free-and-what-it-means-for-developer-tooling-companies-d2cc61d346e9?source=rss----8b6b51da28b5---4</link>
            <guid isPermaLink="false">https://medium.com/p/d2cc61d346e9</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Sanket Saurav]]></dc:creator>
            <pubDate>Tue, 28 Apr 2020 16:41:06 GMT</pubDate>
            <atom:updated>2020-04-28T16:43:30.242Z</atom:updated>
            <content:encoded><![CDATA[<h4>A story of how GitHub embraced the free tier and feature gating, and how everyone else might need to do the same.</h4><p><em>Originally posted on </em><a href="https://sanketsaurav.substack.com/"><em>sanketsaurav.substack.com</em></a><em>.</em></p><p>Last week, GitHub <a href="https://github.blog/2020-04-14-github-is-now-free-for-teams/">announced</a> its all-new Free plan, making GitHub free for all developers and teams with unlimited collaborators and unlimited private repositories. The announcement came as a big surprise for many. GitHub’s business model always has been charging teams for private repositories — while remaining free to use for open-source repositories. With this change, GitHub turned off a significant chunk of its revenue coming from organizations on the Team plan.</p><p>Until you take an in-depth look — which is when you see how this change was a long time coming and shouldn’t have surprised a keen observer, I’ve been watching developer tools closely for quite some time. Pricing changes of platforms like GitHub are of particular interest to me since the <a href="https://deepsource.io/">company I run</a> is a complementing service used by developers.</p><p>To understand how the pricing change was a long time coming, and how it probably doesn’t really impact GitHub’s revenue in the long run, let’s take a few steps back and see how we arrived here.</p><h3>GitHub’s approach to product and pricing</h3><p>GitHub’s business model has always been charging users and teams for private repositories. The product is entirely free to use for open-source code, which brings in massive activity from developers. Once you’re hooked to using GitHub, there’s a high chance that you’ll pay for storing your private code too. Neat.</p><p>Historically, GitHub has never had feature gating of any kind — the free and paid plans get almost identical capabilities. Therefore, the value addition to customers has always been the ability to use GitHub for private code. Since the launch in 2008, the pricing was based on the number of private repositories and had multiple tiers for different brackets of repositories allowed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YRSUH88dWcvQEruN.png" /></figure><p>That changed in 2016 with the announcement of <a href="https://github.blog/2016-05-11-introducing-unlimited-private-repositories/">unlimited repositories</a> — switching the pricing model to the number of users. <strong>The value, still, was using GitHub for storing private code.</strong></p><p>This product strategy (of having no feature gates) and pricing model (free for open-source, paid for private code) proved to be very useful in acquiring users fast — who could quickly get to see the value on open-source code and then swipe a card to use private repositories. The simplicity of the product and a singular focus on no-frills source code hosting and better collaboration tools further accelerated the growth.</p><h3>Comparison with Bitbucket and GitLab</h3><p>Quite the opposite to GitHub, Bitbucket and GitLab have always had feature gates headlining their pricing strategy. Both these platforms have had, unlike GitHub, a free tier for private code. But their pricing has been, in general, complex. For instance, Bitbucket still offers enforced merged checks in their most expensive plan; and GitLab offers the merge approvals only in the paid tier, and multi-group user boards in a higher paid tier. GitHub had been the first mover in providing most of these features and kept all these features available to all tiers.</p><h3>A shift in the user’s perception of value</h3><p>GitLab’s <a href="https://about.gitlab.com/blog/2018/08/16/gitlab-ranked-44-on-inc-5000-list/">meteoric success</a> in the past couple of years brought into light a new trend, however. GitLab went full ballistics with feature gating, with as many as four tiers of pricing — and tried to attack the <a href="https://about.gitlab.com/devops-tools/">entire DevOps category</a> with different product features aimed at various verticals and under different plans. This strategy was new, utterly opposite as compared to what the largest incumbent GitHub was doing, and would have seemed foolish to any observer at that time. And why not? After all, GitHub has been the reigning leader of the category, kept its product simple and focussed, and built an extensive API to play well with complementing services like CIs, issue tracking, code verification, automated deployments, monitoring, release management, etc. GitLab just attempted to do everything, all at once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zlbYaECOWm0QgLbq.png" /></figure><p>But it turns out, GitLab has been a visionary. Their experiments with embracing feature gating uncovered something very unconventional: <strong>hosting private repositories alone is no longer the core value for the customer.</strong></p><p>The world has changed a lot since GitHub’s founding in 2008, and organizations are now embracing workflow automation more and more. The success of CI / CD platforms like Circle CI and Travis CI, the more recent roaring success of dependency vulnerability detection platforms like <a href="https://techcrunch.com/2020/01/21/snyk-snags-150m-investment-as-its-valuation-surpasses-1b/">Snyk</a>, and growing adoption of automated code quality and verification tools clearly meant that engineering teams from companies of all sizes are looking at automating everything in the software development that can be automated — and they’re looking for 3rd party services to do that, as compared to building things internally.</p><h3>Enter, $MSFT</h3><p>It’s mid-2018, and Microsoft announced that it’d <a href="https://techcrunch.com/2018/06/04/microsoft-has-acquired-github-for-7-5b-in-microsoft-stock/">acquire GitHub</a> for a whopping $7.5B in stock. Things had not been exactly rosy at GitHub before that, and the company had struggled to make money despite having built the most influential platform for developers and engineering teams in the world. This story is something every investor dabbling in developer tools loves to quote (in addition to Docker), but that’s a tale for another day.</p><p>With a new leadership under Nat Friedman, GitHub quickly figured out what it had been missing. GitLab had just crossed the $100M ARR mark, and Atlassian’s ~1B ARR saw some decent growth coming from Bitbucket. GitHub had the largest and fastest-growing, user-base of developers from across the world — what would it take to convert that into massive revenue growth?</p><h3>The Big Switch</h3><p>It’s almost like GitHub had this epiphany after the acquisition. It realized the shift in the value chain of software development tooling. It realized that it already had the most massive distribution platform for developers — with 40M+ developers and 2.9M+ organizations — and they no longer needed just private repositories and collaboration tools.</p><p>So GitHub switched the gears to build everything else, just like GitLab — <em>almost</em>. Soon after the acquisition, it went on an acquisition spree, gobbling up <a href="https://pullpanda.com/">Pull Panda</a>, <a href="https://semmle.com/">Semmle</a>, <a href="https://dependabot.com/">Dependabot</a>, and the latest, <a href="https://www.npmjs.com/">npm</a>. It also added <a href="https://github.blog/2019-08-08-github-actions-now-supports-ci-cd/">CI / CD capabilities</a> after refreshing GitHub actions — which, as you’ll see later, will go on to become a significant part of its strategy.</p><p>In a matter of fewer than two years, GitHub switched from being the best code hosting and collaboration platform for developers to trying to be the single platform where software development happens. I’m tempted to use the term OS for Software Development here, but I think the analogy has already been overused.</p><h3>GitHub Free: embracing the inevitable</h3><p>Given the detour we took so far, making it free for all teams and developers seems the natural progression for GitHub. It realized that much more value could be created by selling value-add services on top of source-code hosting, backed by a massive distribution base it has already built. If you look at the latest pricing, this becomes as plain as day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q-lMmqotXFfy_RUw.png" /></figure><p>GitHub has realized what features add the most commercial value for its customers and also has been pushing for more adoption of GitHub actions — for CI / CD and ad-hoc pipeline integrations.</p><p>Embracing feature gating, it moved all essential features to the free tier except for those that teams can’t possibly live without now — like required reviewers (which is something that GitLab did from the very beginning).</p><p>Another evidence is decreasing the free action minutes from 10,000 to 3,000 in the team plan. This signifies that GitHub has seen growth in people adopting GitHub Actions as their primary CI / CD if they’re on GitHub already (bad news for Circle CI) — so the change in pricing based on minutes makes total sense.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8pWgVqDpIfzZUhqx.png" /></figure><p>Soon, we’ll see GitHub adding or moving more additional features only in the paid plan. This is a double whammy — GitHub gets to say it’s free for anyone doing software development in the world, but it’s making sure people who can pay, would pay.</p><p>So yes, GitHub Free has had GitHub lose a lot of revenue in the short-term, but my educated guess is, it’s not a lot. And all that loss would be offset by new teams jumping on board from other platforms like GitLab and Bitbucket and eventually converting to paid in the mid-term future anyway. In the long-term, GitHub Free makes GitHub more revenue.</p><h3>The math for GitHub Free</h3><p>Let’s talk about a team of 10 developers who are on the Team plan. The team also uses GitHub Actions for CI / CD on all their projects, stores built packages using GitHub Packages and also generates a lot of artifacts through GitHub Action runs. It is common for a team of this size and decent activity to use at least 5,000–7,000 build minutes every month.</p><h4>What’d they’d be paying before</h4><pre>$25/mo (for the first 5 users) + $9/user/mo ⨉⁢ 5 users = $70/mo $0 * 7,000 minutes (free build minutes) = $0<br><strong>Total:</strong> <strong>$70/mo</strong></pre><h4>What they’d be paying after GitHub Free⁢</h4><pre>$4/user/mo ⨉ 10 users = $40/mo<br>$0 * 3,000 mins (free build minutes) + $0.008/min * 4,000 mins = $32/mo<br><strong>Total: $72/mo</strong></pre><p>For small teams that are deeply integrated with GitHub, which is something GitHub is betting on anyway, they’d be paying more now. As the team grows in size, yes, the total cost would see some decrease as compared to previously — but there are high chances that more features could go behind more pricing tier, just like GitLab.</p><h3>What GitHub Free means for other developer tools</h3><p>I’ll be honest here — this is not particularly good news for complementing services that engineering teams use in their workflow. Since GitHub has become so ubiquitous amongst tools bought by engineering teams, it has also become a reference point when it comes to pricing. When purchasing a tool that works on top of GitHub (like a CI tool, or code review automation tools), it is prevalent for customers to compare the pricing with GitHub — “<em>Why should I pay $30/user/mo for this tool when I’m just paying $9/user/mo for GitHub?”</em>. Well, this pricing change is just going to make it worse for everyone. The pricing change by GitHub is the last nail in commoditizing source-code hosting in the industry, and like other players, it has now stepped into the value addition game with features on top of the core workflows.</p><h3>Embrace the Free tier</h3><p>Here’s the silver lining. The fact that GitHub is betting on primarily selling value-added services proves business value validation for every developer tooling company out there. If the biggest player in the market is moving towards them, they’re already sitting on a gold mine. Which makes sense — since we’ve seen increasing adoption of tools that automate parts of software development and save developer time</p><p>From a pricing perspective, it makes sense for developer tools who’ve been pricing per user to embrace the free tier, and give at least some user seats for free — if not all. They’ll also need to identify which of their features add the most value, and ruthlessly put everything in the free plan. This will not only help improve adoption but also help focus on the features that add the most commercial value.</p><p>GitHub just validated the larger trend in the developer tooling market, which GitLab and others had already foreseen. Others will need to catch up now for better or for worse quickly.</p><p><em>Originally posted on </em><a href="https://sanketsaurav.substack.com/"><em>sanketsaurav.substack.com</em></a><em>.</em></p><p><em>Thoughts? Ping me on Twitter </em><a href="https://twitter.com/sanketsaurav"><em>@sanketsaurav</em></a><em>, or write a response to this post. Comments or critique are always welcome!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2cc61d346e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sanket-saurav/github-free-and-what-it-means-for-developer-tooling-companies-d2cc61d346e9">GitHub Free and what it means for developer tooling companies</a> was originally published in <a href="https://medium.com/sanket-saurav">reflog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019: In Review]]></title>
            <link>https://medium.com/sanket-saurav/2019-in-review-b3274045e013?source=rss----8b6b51da28b5---4</link>
            <guid isPermaLink="false">https://medium.com/p/b3274045e013</guid>
            <category><![CDATA[stories]]></category>
            <dc:creator><![CDATA[Sanket Saurav]]></dc:creator>
            <pubDate>Tue, 31 Dec 2019 08:21:09 GMT</pubDate>
            <atom:updated>2019-12-31T08:21:09.900Z</atom:updated>
            <content:encoded><![CDATA[<h4>Looking for the truth, and finding it.</h4><p><em>“Do not seek to follow in the footsteps of the wise”</em>, said the great Haiku master and Japanese poet Matsuo Bashō, <em>“seek what they sought.”</em></p><p><strong><em>Seek what they sought.</em></strong></p><p>2019 has been a life-defining year for me. It certainly has been way better than how 2018 went by, but you won’t know that because I didn’t write a <em>2018: In Review</em>. I was too busy fixing my life which had been a shambles. But it’s okay. <em>Better </em>is a relative term anyway.</p><h3>Jumping off the cliff, yet again.</h3><p>I know, I know — it has become quite cliché now. I’m guilty of using this metaphor way too much, but this is precisely what has punctuated 2019 for me. At the end of 2018, I <a href="https://sanketsaurav.com/and-now-for-something-new-9dba87358d48">moved on</a> from the company that I had founded right after college to start <a href="https://deepsource.io/">a new one</a>. I practically moved on from over 4 years of hard work for zilch, and started from square one again. This time, a little wiser.</p><p>Jai and I put all that we had into it, borrowed what we needed to fill the gap, and flew to San Francisco in April after we had launched DeepSource in March 2019. The next three months would determine the future of the company, and we knew that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VhiCT8soem1cbboKjwNBDQ.jpeg" /><figcaption>I still remember seeing the Bay Bridge at night for the first time. This place still mesmerizes me.</figcaption></figure><p>We hit the ground, and we did it hard. Starting with practically zero connections in San Francisco and the Valley, I reached out to anyone and everyone who could help us. Many didn’t return calls and messages, but a few did. I’m immensely grateful to everyone who extended a helping hand, lent an ear and gave advice — you know who you are.</p><p>Soon, we onboarded <a href="https://github.com/uber/ludwig">Uber</a>. <em>Bingo. </em>Turns out, people <em>did </em>want what we were building and it was not just in our heads.</p><p>We also convinced some trusted advisors to get associated with the company, officially. Here’s Brad, who saw DeepSource from the time it was merely an idea, when he wrote us our first cheque.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A6ldcQk0m1vlQbplTS6qIw.jpeg" /><figcaption>I had foreseen that I wanted to use this photo in a blog post. Cha ching!</figcaption></figure><p>We also traveled to Cleveland and presented DeepSource at PyCon US.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FOvahOAQb1vVtXxrlHiy-g.jpeg" /><figcaption>Dorky doesn’t even begin to explain this photo.</figcaption></figure><p>And I got to meet <a href="https://en.wikipedia.org/wiki/Guido_van_Rossum">Guido</a>! Talk about dreams coming true.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mvH1Wgm647HAeRY1XhzrzQ.jpeg" /><figcaption>Couldn’t control that grin.</figcaption></figure><p>Heck, I even learned how to cook spaghetti!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pbbSnhSbtcn86XnLadvlyA.jpeg" /></figure><h3>Assembling the pack, yet again.</h3><p>We came back to India in July after being almost satisfied with how the trip had been. It could have been better, sure. But I wasn’t complaining. What seemed like the hardest part now seemed relatively easy. I’ve always maintained that hiring is the most important part of building a company. A company, after all, is defined by its people — it’s success determined by how badly these people want that success. Hiring mistakes can be fatal as I had experienced first hand, and I didn’t want to make the same ones I made the last time.</p><p>Some of my ex-colleagues left their cushy jobs to work with us at DeepSource. These are some of the smartest people I’ve known. Nothing feels more humbling than having them put their faith in me yet again. This is something money can’t buy.</p><p>Some familiar faces, and some new ones. I’m so proud of the team we’ve put together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tAXyYi1H97T0VitKh74I3w.jpeg" /></figure><h3>Thankful, yet again.</h3><p>It’s surreal how some people stand by you through thick and thin, all the time. These are people you can trust, and if you have someone like this, hold them dear.</p><p>I’m grateful for some people in my life who did the same this year. Thanks for all the love and support — in more ways than you would know. I’m not going to name the names, because you know who you are.</p><p>2019 has been good. It has been the year I put everything I had on the line yet again and tasted some success. But it’s just the beginning, and 2020 holds many great things. 2020 is going to be better.</p><p>But better is a relative term anyway.</p><p><em>— Sanket.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3274045e013" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sanket-saurav/2019-in-review-b3274045e013">2019: In Review</a> was originally published in <a href="https://medium.com/sanket-saurav">reflog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Messiah Hire Fallacy]]></title>
            <link>https://medium.com/sanket-saurav/the-messiah-hire-fallacy-325b663f2691?source=rss----8b6b51da28b5---4</link>
            <guid isPermaLink="false">https://medium.com/p/325b663f2691</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Sanket Saurav]]></dc:creator>
            <pubDate>Mon, 24 Jun 2019 03:16:56 GMT</pubDate>
            <atom:updated>2019-06-24T03:18:53.360Z</atom:updated>
            <content:encoded><![CDATA[<h4>Falling in love hardly ever saves a company.</h4><p>Things can go wrong very often at startups. Sometimes when the impact is pretty evident, there’s a chance of rectification right away. At other times watch things go wrong over a stretch of time bit by bit, letting the damages accrue, and the consequences present themselves only when the proverbial sand is out of the hand.</p><p>Now, the most common reaction of leaders when they hit the second scenario in a sudden stroke of realisation is panic. Since the damages have accrued over time, it becomes almost impossible to get a grip on the situation. Now instead of looking at a solution <em>inward, </em>which is where the solution is most likely to be, the leaders start looking at the easier way. <em>Outward.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Lid9opwdeiktHxlV" /><figcaption>Photo by <a href="https://unsplash.com/@jamesoliverbarr?utm_source=medium&amp;utm_medium=referral">James Barr</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>All organizational problems have a solution inward. But looking inward for a solution mean deep introspection, which often leads to discovering one’s own faults. It involves uncomfortably probing into the hot mess that your organization is right now, asking difficult questions, and taking the hard decisions.</p><p>Looking outward is easy. You get to turn a blind eye to all that’s wrong and put all your hope for a better tomorrow on a shiny new thing which is <em>guaranteed to solve all that’s broken right now</em>.</p><p>This shiny new thing takes many forms: a new product line, a new strategy, or a new hire. We’ll talk about the last one.</p><p>Enter the Messiah<em>. </em>The new hire who’ll seemingly solve all problems and more, magically! The leaders fall in love with this new hire who’s supposedly going to save them and the company and put unrealistic hopes and expectations from this person. I’ve been there. So have a lot of other founders, especially first-timers. I’m here to tell you, it’s the worst mistake you’ll ever do.</p><h3>Never hire when you’re desperate.</h3><p>The <em>magic </em>never happens. Consider the following reasons:</p><ol><li>A startup is a team effort, and it is incredibly rare — almost impossible, for someone to just drop in and solve some intractable problem. There is no rational argument that can support this premise.</li><li>In desperation, it is common to make bad hiring decisions, primarily because you end up looking for a <em>messiah</em> rather than a proper fit. Instead of empirically and objectively judging someone’s competence, it is very common to look at signals — fake indicators of virtue. <em>What works for others most definitely wouldn’t work for you</em>.</li><li>By bringing a messiah, the leaders most definitely end up disrupting the existing order in the team. In times of crisis, the last thing people should worry about is that they’re going to report to someone new from tomorrow.</li></ol><p><a href="https://medium.com/u/743941d2a352">Anand Sanwal</a>, in his brilliant <a href="https://www.saastr.com/anand-sanwal-cb-insights-dont-68-things-saas-company-video-transcript/">SaaStr Annual</a> talk, mentions the Messiah Hire Fallacy as one of the screw-ups to avoid at a startup. This is something that a lot of startups end up doing. For some, the consequences are grimmer than others.</p><p><em>What do you think? Let me know </em><a href="https://twitter.com/sanketsaurav"><em>@sanketsaurav</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=325b663f2691" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sanket-saurav/the-messiah-hire-fallacy-325b663f2691">The Messiah Hire Fallacy</a> was originally published in <a href="https://medium.com/sanket-saurav">reflog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The refreshing power of balance]]></title>
            <link>https://medium.com/sanket-saurav/the-refreshing-power-of-balance-70bec897db09?source=rss----8b6b51da28b5---4</link>
            <guid isPermaLink="false">https://medium.com/p/70bec897db09</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[duality]]></category>
            <category><![CDATA[stories]]></category>
            <category><![CDATA[philosophy]]></category>
            <dc:creator><![CDATA[Sanket Saurav]]></dc:creator>
            <pubDate>Sat, 02 Feb 2019 16:10:42 GMT</pubDate>
            <atom:updated>2019-02-03T04:45:34.793Z</atom:updated>
            <content:encoded><![CDATA[<h4>How breaking away from extremities opens up immense possibilities.</h4><p>As kids, we are brought up to believe in the existence of black and white. There’s good, and there’s bad. Right and wrong. Angels and demons. Gods and, well, not gods. We are brought up to believe in a certain dichotomy of the universe, and we grow up believing in the ubiquity of this duality.</p><p>By the time we are <em>actively conscious</em>, which is when we start thinking for ourselves, our worldview has formed around this supposed duality. We start thinking about everything in terms of <em>good </em>and <em>bad.</em> The moment we have a new experience, we rush to classify them into either of these buckets. People, experiences, actions — they can either be right, or wrong. Rarely is there something in between.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T9t7L7koN31MZMxf_vlYgw.png" /><figcaption>Rumi understood the delusion of this duality like nobody else.</figcaption></figure><p>A direct result of this is we start thinking in terms of <em>extremes</em>. We fail to acknowledge the continuum that permeates our existence and start believing in discrete functions. It becomes impossible to imagine there’s any other option apart from believing in God or not, for example. We think we fall into either of these buckets: rich or poor, successful or unsuccessful, beautiful or ugly, happy or unhappy.</p><p>Most importantly, we think there are only two ways of following an ideology — to follow it completely, or not follow it at all. We quickly associate these two options with, you guessed it, right and wrong. And the gavel of judgment bangs.</p><h3>The truth lies in the continuum.</h3><p>Turns out, this approach of looking at things in either black or white is incredibly prohibitive on our abilities and the possibilities of what we can do. The mental block of trying to either follow something completely or not at all is exhausting and not very productive. It hinders our ability to improvise and forces us to think in discrete values instead of fluidity. There is a whole world of possibilities in the grey.</p><p>If we break away from the compulsion of either following or not follow something <em>in its entirety</em>, we suddenly have a lot of room to grow. Amidst two choices of doing something, it’s possible to carve out a third solution which can possibly take the best parts of either of the two extremities.</p><p>Once we’re at peace with not following any extremities, we get to see how liberating that is. After that, it’s very easy to get used to this balance. That feeling, as I’ve personally experienced, is life-transforming.</p><h3>Balance as a way of life.</h3><p>In our everyday lives — personal and professional, we face these kinds of choices in plenty. Every once in a while, when taking a decision, two prominent choices will present themselves, possibly among many others. Naturally, and intuitively, your mind will rush to classify them as <em>right </em>and <em>wrong</em>, inevitably implying that one of them is the one you should choose and not the other one.</p><p>But next time that happens, pause and think — what if none of them is <em>right </em>or <em>wrong? </em>If you come to terms with that fact, it becomes easy to find <em>your </em>right choice that aligns with your principles.</p><p>That, I will argue, is a pretty good way of living our lives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70bec897db09" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sanket-saurav/the-refreshing-power-of-balance-70bec897db09">The refreshing power of balance</a> was originally published in <a href="https://medium.com/sanket-saurav">reflog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[And now for something new…]]></title>
            <link>https://medium.com/sanket-saurav/and-now-for-something-new-9dba87358d48?source=rss----8b6b51da28b5---4</link>
            <guid isPermaLink="false">https://medium.com/p/9dba87358d48</guid>
            <category><![CDATA[personal]]></category>
            <category><![CDATA[stories]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Sanket Saurav]]></dc:creator>
            <pubDate>Mon, 21 Jan 2019 08:06:18 GMT</pubDate>
            <atom:updated>2019-01-27T22:15:20.024Z</atom:updated>
            <content:encoded><![CDATA[<h4>I have a life update.</h4><p>The pursuit of truth, as they say, is a noble undertaking. Seeking what our innate nature is, and aligning our life with it is a great way of living out our rather short lives.</p><p><em>Truth will not make us rich, but it will make us free.</em></p><p>I had started DoSelect with my college room-mate right after graduating in 2014 as we moved to Bangalore, the city of dreams for anyone who wanted to build a startup. With a head full of ambitions and a wallet bereft of cash, we built a world-class technical assessment platform from scratch, helped numerous companies make their hiring funnels more effective, and added value to products of many partners in the last four years. Starting from absolute zero, we were able to achieve something that the entire team has been proud of.</p><p>Personally, I evolved with the company. Apart from learning to build products, I also learned the various intricacies of the human condition while hiring colleagues and managing teams. I had never worked in a team before but I came to understand the true meaning of leadership, loyalty and trust when I got to lead my amazing colleagues at DoSelect.</p><blockquote>“It is not our abilities that show what we truly are. It is our choices.”</blockquote><p>As the adage goes — <em>Change is the fuel of nature.</em> When the din of glamour has faded, the sound of truth becomes deafening. Over the period of 2018, through all our ups and downs, slight swerve at times, I came to discover that there had emerged a fundamental misalignment between myself and other stakeholders of the company.</p><p>I began to seek an answer to whether I am doing justice to <em>myself</em> by doing what I am doing. We had shifted lanes to a path that would no longer take us to a place which I had envisioned for the company the way I wanted to, for all I could have tried. In retrospect, it occurs how we must all, at one point, face the choice between what is right and what is easy. It was time for me to move on. I decided to part ways with the company. <strong>As of October 31st, 2018 I am no longer associated with DoSelect in any capacity.</strong></p><p>I’ve had the privilege of working with some of the brightest people in my team, for most of which DoSelect was their first job. Many of these colleagues have become trusted friends and advisors. I will be eternally grateful to all our investors who trusted us early on when nobody else would and helped DoSelect come thus far.</p><p>It has been an extremely difficult decision because I had lived and breathed DoSelect for the past four years of my life. But the decision was easy too because I knew this is what I really wanted to do. I will be immensely grateful to my parents, my brother, and my close friends who stood by me and helped me get through this. I would forever be indebted to Nivedita for being there when it mattered. Finally, I cannot thank everyone associated with DoSelect enough who put their faith in me till the end — you know who you are.</p><h3>What’s next for me?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bpImPrEn8o0PQKgEqIZ76g.jpeg" /><figcaption>From Ray Dalio’s <strong>Principles</strong>, a book that changed my life.</figcaption></figure><p><strong>I am building </strong><a href="https://deepsource.io/"><strong>DeepSource</strong></a><strong>, along with my ex-colleague and trusted friend Jai. We have a new mission — helping developers ship lesser bugs.</strong></p><p>While shipping software and managing engineering teams for four years, I battled with numerous problems related to developer tooling and processes for maintaining the health of code. I’ve witnessed our own team battle from increasing technical debt. Many of my peers who run their own startups and manage engineering teams had something similar to say.</p><p>I believe there is a better way of doing this. Developer tooling has been an area of great interest to me personally, and I’m super stoked to be able to work on something which is so close to my heart. I’m excited for what’s about to come, what we build, and where we reach. <em>The best way to predict the future is to create it.</em> <strong>Here’s us taking a shot at creating the future, one in which tools to deliver reliable software, faster are accessible to everyone.</strong></p><p>Thank you for reading. I wish you have a great year ahead. Onward and upward! 🚀</p><p><em>— Sanket.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dba87358d48" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sanket-saurav/and-now-for-something-new-9dba87358d48">And now for something new…</a> was originally published in <a href="https://medium.com/sanket-saurav">reflog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A blissful dullness]]></title>
            <link>https://medium.com/sanket-saurav/a-blissful-dullness-daa64a86baeb?source=rss----8b6b51da28b5---4</link>
            <guid isPermaLink="false">https://medium.com/p/daa64a86baeb</guid>
            <category><![CDATA[stories]]></category>
            <category><![CDATA[personal]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Sanket Saurav]]></dc:creator>
            <pubDate>Wed, 12 Dec 2018 19:54:23 GMT</pubDate>
            <atom:updated>2018-12-14T14:54:26.750Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve come to visit my parents in <a href="https://goo.gl/maps/hvTQUCWQdf32">Purnea</a> after quite a while, and at a time when there are absolutely no festivities around — in my family or otherwise. This has been <em>very </em>relaxing for me since there had been something or the other going on every time I’ve been here in the past three years.</p><p>It’s times like these when you actually get to experience the blissful dullness of a small town — not during a festival where everyone’s dressing up and trying to reach <em>somewhere </em>on time — but this. It’s the onset of winter, with a wee-bit of chill in the evening air. Everything, and everyone, seems so calm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l4EL_vYILRPKK0YZZTuz_w.jpeg" /><figcaption><a href="https://www.google.com/search?q=bhatta+bazar">Bhatta Bazaar, Purnea</a></figcaption></figure><p>Stay too long at a stretch in a city like Bangalore and it calibrates how soon you expect things to happen. I book a cab and expect it to be at my door in 10 minutes; or order food online and start getting antsy if it isn’t there in 20. Or an Amazon delivery in a couple of days.</p><p>Not here. Not a chance. The arc of time has a longer horizon here, and everyone seems to be <em>okay </em>with it. Happily okay, not compromisingly okay. I feel that alien, yet refreshing. Calming, even.</p><p>I had taken my mum shopping, and I realized to my utter astonishment that the place (it’s a one-kilometre stretch bustling with shops on either sides) hasn’t changed <em>at all </em>since the last I visited it and have since tried to preserve it in my memory from about 10 years ago. Same old shops, same old typography on the hoardings, same old people, same old <em>air</em>.</p><p>It’s funny how deeply we have been conditioned to expect how soon we’ll get to see change. Maybe it’s a fool’s pursuit to be in a rush all the time. Maybe things <em>do </em>take time. Maybe it is what is best for us.</p><p>Sometimes there are hidden life lessons in places where you’d least expect them to be. For me, that turned out to be a mundane evening stroll in the bustling market of my hometown.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=daa64a86baeb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sanket-saurav/a-blissful-dullness-daa64a86baeb">A blissful dullness</a> was originally published in <a href="https://medium.com/sanket-saurav">reflog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What are the engineers building?]]></title>
            <link>https://medium.com/sanket-saurav/what-are-the-engineers-building-fc7890eae7fd?source=rss----8b6b51da28b5---4</link>
            <guid isPermaLink="false">https://medium.com/p/fc7890eae7fd</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Sanket Saurav]]></dc:creator>
            <pubDate>Sun, 27 May 2018 13:15:01 GMT</pubDate>
            <atom:updated>2018-05-27T13:15:01.035Z</atom:updated>
            <content:encoded><![CDATA[<h4>A high-order metric for measuring startup success.</h4><p><em>“You can’t improve what you can’t measure”</em> is probably the most commonplace aphorism you would hear in startup circles — among founders, execs, growth hackers, <em>hustlers, </em>et al. What you measure, of course, depends largely on your context. <a href="https://www.forbes.com/sites/theyec/2014/06/20/the-seven-startup-metrics-you-must-track/#294b4af4725e">A</a> <a href="https://a16z.com/2015/08/21/16-metrics/">great</a> <a href="https://www.forentrepreneurs.com/saas-metrics-2/">deal</a> has been written about metrics you should take seriously, and you can choose what suits you best. An important thing you’ll notice is that all these metrics are essentially outward facing metrics. These metrics are also of the first-order and can be measured directly.</p><p>In addition to these, I’ve realized that second-order metrics provide a higher-level view of a company’s progress over a longer time horizon. These metrics are introspective in nature, as opposed to outward facing like the metrics I mentioned earlier. They’re not very straightforward to measure but are very easy to understand nonetheless. And they uncover a number of things that the first-order metrics will miss.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*thVtNQFMLBP_WZmRaib23w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/hCb3lIB8L8E?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Annie Spratt</a> on <a href="https://unsplash.com/search/photos/working?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>What the engineering team is spending time on is one such metric. In most product startups, what the engineering team’s building can be categorized into two broad buckets: optimizing existing stuff, and building new things.</p><p>When the company is in its nascent phases and doesn’t have a product-market fit, nobody really knows what’s going to work. So they <em>speculate </em>what could work, and the engineering team spend their building new, speculative things. As time passes and the company gains users for these speculative things, the product inches closer to a market fit. The focus of the engineering team now must gradually shift towards optimizing these existing products as opposed to continue building new things. The ratio of time spent on optimization vs. building new things keeps increasing as the scale of usage of the product increases. And this becomes a necessity as well: hitting scale opens a Pandora’s box of problems that didn’t exist before. The code that worked well for the MVP a year back must be refactored and cleaned, lest it hold back the new people who’ve joined the development team. You must work on adding a robust caching layer now, and yeah — you’re probably going to need to rewrite that subsystem in Go because the existing implementation chokes up when concurrent requests burst. ¯\_(ツ)_/¯</p><p>In mature product companies, the engineers spend 70%-80%<strong> </strong>of their bandwidth in optimizing the existing products that serves most of their user base. Most of these changes are invisible to the users, even the internal non-engineering teams. These changes, one could argue however, are what sustain the product growth. The rest of the time and effort goes in building new, speculative things — hoping that some of these might cross in the former category in the near future.</p><p>A visible proof of this is easy to detect: take any popular application that you’ve been using for a long time — like Gmail, Facebook, or Uber. Now think about the last time you had noticed a major change in the existing UI or workflows, or addition of a new feature. Although you might notice, the one essential thing that you do in these apps has somehow kept on improving. If there are changes, they are in these core workflows to make them better.</p><p>Here’s another way to look at this metric: it can indicate the business progress of the company and provide an early sign of impending trouble. If the engineering team is regularly working on new things and not spending time with the existing code base, it clearly means non-adoption of existing products and non-achievement of product-market fit yet. If these new things are major new products, then each of these can be termed as <em>pivots</em>. It’s normal for companies to try multiple things before finding their fit — many great companies have taken up to 3 years to achieve it. But a recurring pattern of jumping on new things is generally a sign of serious trouble.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc7890eae7fd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sanket-saurav/what-are-the-engineers-building-fc7890eae7fd">What are the engineers building?</a> was originally published in <a href="https://medium.com/sanket-saurav">reflog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mother]]></title>
            <link>https://medium.com/sanket-saurav/mother-4a5ed1cd44c7?source=rss----8b6b51da28b5---4</link>
            <guid isPermaLink="false">https://medium.com/p/4a5ed1cd44c7</guid>
            <category><![CDATA[personal]]></category>
            <category><![CDATA[mothers]]></category>
            <dc:creator><![CDATA[Sanket Saurav]]></dc:creator>
            <pubDate>Sun, 01 Apr 2018 12:39:08 GMT</pubDate>
            <atom:updated>2018-04-04T15:10:30.180Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1pG7B3Wa_TD1G80D_aP2Iw.jpeg" /><figcaption>I wish I had more of her good looks genes. ¯\_(ツ)_/¯</figcaption></figure><p>I doubt anyone else has had a greater impact on my life than my mother. But I’m sure that’s true for most people. Mothers, in general, tend to have a deep impact on lives, both of their children and everyone else in the family. So yeah, this story is not unique. But this story is about a special woman, and it deserves to be told.</p><p>It would be an understatement if I called my mother a strong woman. Consider this: She got married young into a joint family in a small town in Bihar, managed to get a masters degree in Political Science while raising two brats (me and my brother), got a fine-arts degree on the side, started a successful arts school, and still solves the big and small problems for the two brats in her life and for my dad. And she has managed to do all this without practically breaking a sweat. It’s been 25 years since she’s been married to my Dad, and she’s done this every single day, selflessly. This has taken a toll on her body, but she doesn’t care. Because that’s a mother for you.</p><p>I often think about how little appreciation mothers get for all the work they’ve done and continue to do without anyone asking for it. I’ve been guilty of the same. Rarely have I told my mother how much I appreciate all that she’s done for me, for all that she’s continuing to do for me even if I’m supposed to be this responsible adult person living two thousand kilometers away from her. She’s still the first person I call when my mind’s not at peace, and she knows it before I’ve had the chance to even tell her.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*oXcizhZqu37Uh_HQ6H9MRw.jpeg" /></figure><p>I’ve often sneakily caught her beaming with pride while telling her friends about my own exploits and achievements — which are not very much of a big deal for anyone else except her. But I have realised that probably I’ve never stopped for a moment and appreciated all of <em>her </em>achievements, all of <em>her </em>exploits.</p><p>So this is me, beaming with pride, for having the fortune of being raised by you, Mother. You are the strongest, most determined and hard-working woman I’ve ever known in my life. You have set the example for what excellence means for me. Whatever I might do in life, wherever I might reach — all my successes would be attributed to you.</p><p>You have imparted some great values in your children — of integrity, honesty, and respect for other human beings. Traits that you possess yourself naturally.</p><p>You have taught me to never shy away from dreaming big regardless of the adversities staring at me,</p><p>You have taught me that there’s no alternative for success other than working hard, working honestly, and always getting back up after a failure.</p><p>You have taught me to never succumb to dogma or follow the herd, to be radically open-minded and think independently.</p><p>You have taught me that being happy is more important than being successful. And that chasing happiness will eventually bring success.</p><p>In retrospect, I think all this would have come naturally to you because you, Mother, have been a teacher first. You have changed lives of hundreds of your students. And you have changed mine.</p><p>Happy birthday, Mother.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a5ed1cd44c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sanket-saurav/mother-4a5ed1cd44c7">Mother</a> was originally published in <a href="https://medium.com/sanket-saurav">reflog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>