<?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 Nemil Dalal on Medium]]></title>
        <description><![CDATA[Stories by Nemil Dalal on Medium]]></description>
        <link>https://medium.com/@nemild?source=rss-544d9b0e147e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nCo06-RrapryoT8k7NH6LA.jpeg</url>
            <title>Stories by Nemil Dalal on Medium</title>
            <link>https://medium.com/@nemild?source=rss-544d9b0e147e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 06:59:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nemild/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 Blockchain Wars]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@nemild/the-blockchain-wars-ae14ce7ebf18?source=rss-544d9b0e147e------2"><img src="https://cdn-images-1.medium.com/max/1000/1*FDT6J8wvdCuvfyaDakp3bg.jpeg" width="1000"></a></p><p class="medium-feed-snippet">The war to be the blockchain that rules them all</p><p class="medium-feed-link"><a href="https://medium.com/@nemild/the-blockchain-wars-ae14ce7ebf18?source=rss-544d9b0e147e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@nemild/the-blockchain-wars-ae14ce7ebf18?source=rss-544d9b0e147e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae14ce7ebf18</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Nemil Dalal]]></dc:creator>
            <pubDate>Tue, 19 May 2020 13:26:00 GMT</pubDate>
            <atom:updated>2020-05-19T13:26:00.914Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Announcing the Coinbase USDC Bootstrap Fund]]></title>
            <link>https://medium.com/the-coinbase-blog/announcing-the-coinbase-usdc-bootstrap-fund-ed5e16ca4daf?source=rss-544d9b0e147e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed5e16ca4daf</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[usdc]]></category>
            <category><![CDATA[decentralized-finance]]></category>
            <category><![CDATA[coinbase]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Nemil Dalal]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 17:01:01 GMT</pubDate>
            <atom:updated>2019-09-10T18:44:30.132Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Coinbase is contributing to the emerging DeFi ecosystem with USDC</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wdwpCQP6_1OXiTO4" /></figure><p>In 2018, the Centre Consortium — which includes Coinbase and Circle — launched <a href="https://www.coinbase.com/usdc">USDC</a>, a stable, secure, and transparent stablecoin. Since then, it has become one of the world’s most popular and trusted stablecoins.</p><p>To encourage further growth in decentralized finance (DeFi), Coinbase is announcing the <em>USDC Bootstrap Fund</em>. The Fund will support developers building DeFi protocols by investing USDC directly in the protocol. Unlike more traditional investments, this money is tied up in a smart contract protocol with return provided by a counterparty (a borrower or taker).</p><p>In our talks with countless developers, we consistently heard how hard it was to get liquidity for a new DeFi protocol. With the Bootstrap Fund, we aim to make it easier for developers to launch their protocol and help them to create healthy, liquid marketplaces by leveraging USDC. The USDC Bootstrap Fund is separate from <a href="https://ventures.coinbase.com">Coinbase Ventures</a>, the venture arm of Coinbase which has made 50+ traditional equity investments in projects across the cryptocurrency ecosystem.</p><p>Through the investment of USDC, our goal over time is to support DeFi teams in making their products safer, and more reliant and accessible than existing financial products. We view this as just one first step for how Coinbase will support DeFi. In the coming months, we’ll share our learnings and future integrations with the community.</p><p>We are also announcing today our first two investments: Compound and dYdX. Coinbase has added 1 MM in USDC to <a href="https://compound.finance">Compound</a>, a money market protocol. We will also add 1 MM in USDC to <a href="https://dydx.exchange">dYdX</a>, a margin trading protocol and open trading platform for crypto assets. In both cases, the USDC tokens are available to borrow by any counterparty willing to provide crypto collateral and pay a floating interest rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pvMfablk5WGlPGf9" /></figure><p>We encourage all DeFi developers and smart contract projects that want to integrate USDC to apply for the USDC Bootstrap Fund. To apply, <a href="https://docs.google.com/forms/d/1FlYKXPyk15k552cU4ezKFempONcLKAyXodN9fXX5g3g/viewform?edit_requested=true">please fill out this form</a>.</p><p><em>Authors: </em><a href="https://medium.com/u/544d9b0e147e"><em>Nemil Dalal</em></a><em> (</em><a href="https://twitter.com/nemild"><em>Twitter</em></a><em>), </em><a href="https://medium.com/u/3898d6f79e89"><em>Jacob</em></a><em> Horne (</em><a href="https://twitter.com/js_horne"><em>Twitter</em></a><em>), </em><a href="https://medium.com/u/6e7a86765482"><em>Daniel Que</em></a><em> (</em><a href="https://twitter.com/danielque"><em>Twitter</em></a><em>)</em></p><p><em>This website may contain links to third-party websites or other content for information purposes only (“Third-Party Sites”). The Third-Party Sites are not under the control of Coinbase, Inc., and its affiliates (“Coinbase”), and Coinbase is not responsible for the content of any Third-Party Site, including without limitation any link contained in a Third-Party Site, or any changes or updates to a Third-Party Site. Coinbase is not responsible for webcasting or any other form of transmission received from any Third-Party Site. Coinbase is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement, approval or recommendation by Coinbase of the site or any association with its operators.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed5e16ca4daf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-coinbase-blog/announcing-the-coinbase-usdc-bootstrap-fund-ed5e16ca4daf">Announcing the Coinbase USDC Bootstrap Fund</a> was originally published in <a href="https://medium.com/the-coinbase-blog">The Coinbase Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why there’s so much burnout in software and what to do about it]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/hackernoon/why-theres-so-much-burnout-in-software-and-what-to-do-about-it-4ef0297ca7cc?source=rss-544d9b0e147e------2"><img src="https://cdn-images-1.medium.com/max/2048/1*0nyiQAs1ik8Wfp3Io5QCoQ.jpeg" width="2048"></a></p><p class="medium-feed-snippet">Tips to beat burnout for early software engineers.</p><p class="medium-feed-link"><a href="https://medium.com/hackernoon/why-theres-so-much-burnout-in-software-and-what-to-do-about-it-4ef0297ca7cc?source=rss-544d9b0e147e------2">Continue reading on HackerNoon.com »</a></p></div>]]></description>
            <link>https://medium.com/hackernoon/why-theres-so-much-burnout-in-software-and-what-to-do-about-it-4ef0297ca7cc?source=rss-544d9b0e147e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ef0297ca7cc</guid>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[burnout-in-software]]></category>
            <dc:creator><![CDATA[Nemil Dalal]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 11:49:29 GMT</pubDate>
            <atom:updated>2019-07-02T01:39:49.620Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[One secret to becoming a great software engineer: read code]]></title>
            <link>https://medium.com/hackernoon/one-secret-to-becoming-a-great-software-engineer-read-code-467e31f243b0?source=rss-544d9b0e147e------2</link>
            <guid isPermaLink="false">https://medium.com/p/467e31f243b0</guid>
            <category><![CDATA[read-code]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[hackernoon-top-story]]></category>
            <dc:creator><![CDATA[Nemil Dalal]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 11:12:51 GMT</pubDate>
            <atom:updated>2019-04-17T14:19:45.198Z</atom:updated>
            <content:encoded><![CDATA[<h4>Become a better programmer by building a routine and habit for reading code</h4><p><em>This is a post in my occasional series, </em><a href="https://www.nemil.com/on-software-engineering/index.html"><em>Notes to a Young Software Engineer</em></a><em>. Sign up </em><a href="http://eepurl.com/cxs5Zr"><em>here</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3P-YM5wfTlx1Aw5LVyEK2Q.png" /><figcaption>A code snippet from <a href="https://github.com/antirez/redis">Redis</a></figcaption></figure><p>If you woke up one day resolved to be a great writer, you’d hear two simple pieces of feedback: write a lot, and read even more.</p><p>In software, plenty of people write code, but precious few spend time reading it — especially code outside their day to day work. That is a mistake. Early in your career, act like an aspiring writer and embrace reading diverse code.</p><p>Read widely and read often. It could be the difference between being a decent software engineer and a great one.</p><h4>Why should I read code?</h4><p>Great writers are a function of the writers they’ve read. Think of Joan Didion, who <a href="https://www.theparisreview.org/interviews/3439/joan-didion-the-art-of-fiction-no-71-joan-didion">typed out Hemingway’s sentences</a> at 16, so she could learn how sentences work. Or think of Abraham Lincoln, whose later lyricism <a href="http://www.abrahamlincolnsclassroom.org/abraham-lincoln-in-depth/abraham-lincoln-and-the-bible/">sprung from his beloved</a> King James Bible.</p><p>Similarly, seeing diverse coding practices lets you expand your palette when it comes time to write your own code. Reading others’ code exposes you to new language functionality and different coding styles.</p><p>Reading your dependencies will make you a more productive programmer. You’ll know the full functionality your dependencies offer. You’ll know exactly how they work and what tradeoffs they’re making. You’ll know where to debug when things go wrong.</p><p>Being comfortable reading code also reduces the likelihood that you’ll overly favor your code. The more you read, the more comfortable you’ll feel augmenting someone else’s code, rather than building your own. This change will reduce the likelihood you’ll be bitten by the “not invented here” syndrome.</p><p>Whether you are a web developer, data engineer, or cryptographer, cultivating regular reading will teach you tools and products different from your day-to-day work.</p><p>As a web frontend engineer, reading a small part of a <a href="https://news.ycombinator.com/item?id=13563577">raytracer’s codebase</a> will expose you to a wholly different set of constraints. As a database engineer, reading high-abstraction web code can show you how your users think. For all engineers, you’ll find value in periodically reading languages outside the one you work with each day.</p><p>As Donald Knuth <a href="http://www.gigamonkeys.com/code-reading/">remarks</a>, “[reading code] is really worth it for what it builds in your brain. The more you learn to read other people’s stuff, the more able you are to invent your own in the future …”</p><p>Here’s how to make your code reading as painless and productive as possible.</p><h4>How should I “read” code?</h4><p>Approaching a codebase like you would a typical book — reading from start to end — is a <a href="http://www.gigamonkeys.com/code-reading/">recipe for failure</a> (though, ironically, this is how computers read code themselves).</p><p>Reading from the start means ignoring important context and having no sense for the structure that is to come. Passive reading — where you don’t write tests or fix bugs — prevents you from truly internalizing the code.</p><p>Unlike a book, nearly all my friends struggle to read code without a particular goal in mind. Before reading a new code base, make sure you have a goal for what you want to achieve. This will make the codebase seem more manageable and provide motivation when the journey inevitably gets hard.</p><p>I use a four-part strategy for approaching any complex code base (RSDW for short):</p><ul><li><strong>(R)un</strong>: compile, run, and understand what the code is supposed to do.</li><li><strong>Examine (S)tructure</strong>: Learn high level structure and review key integration tests.</li><li><strong>(D)ive in</strong>: Follow key flows and read important data structures.</li><li><strong>(W)rite tests</strong>: Write tests and prioritize simple features and bug fixes.</li></ul><p>The RSDW method is a starting point, but over time, you should customize it to what works for you. Some people swear by writing tests and fixing bugs, while others always like starting by reviewing the integration tests.</p><p>At first, though, start with the RSDW method.</p><h4>1. Run</h4><p>The first step in reading code isn’t to actually read code. It’s to use the software.</p><p>Read code only once you have an understanding for what functionality the software offers. During this stage, you should be able to make a summary of the code and have an understanding what the inputs and outputs are.</p><p>Using the software forces you to get it to run. That means tracking down dependencies and, in some languages, compiling the code. For libraries, it means calling a few of the popular functions. This is the time to run tests and review the output messages.</p><p>If you have trouble getting the system running on the first go, it’s the perfect time to document for others what it actually takes to run the software.</p><h4>2. Structure</h4><p>Next, identify the most critical parts of the code. This process is the part that is most different from reading a book. Instead of beginning at the beginning, you have to jump around to identify the key nexuses in the code.</p><p>Start with understanding the structure of the code. At minimum, run a few automated tools (such as tree and cloc) to figure out the languages and files of the codebase.</p><p>To identify the key files, look at the most modified files and use <a href="https://github.com/gilesbowkett/rewind">any other advanced tools</a>. Review the most important integration tests, listing out the functions that are called. Flag these tests for later.</p><p>There’s an easy way to short circuit this process too: find someone who’s worked on the code before. Understanding the structure is a good first task for a whiteboard session.</p><h4>3. Deep Dives</h4><p>Once you have a lay of the land, dig in.</p><p>When reading code, you should look at code flows (seeing the actions that are being created) and look at data structures/objects (where the results of actions are stored).</p><p>Pick three to five critical flows you’ve found from key integration tests, important PRs, or your review of the source files. Then dive deeper. Start at the top of a specific action and trace the code through. Some developers swear by debuggers that let you step through. Others prefer building <a href="https://en.wikipedia.org/wiki/Unified_Modeling_Language">Unified Modeling Language</a> (UML) diagrams or <a href="http://www.brendangregg.com/flamegraphs.html">flame graphs</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*wQeYSmfQsefTlPcClr7f5Q.png" /><figcaption>FlameGraph</figcaption></figure><p><em>Source: </em><a href="https://github.com/brendangregg/FlameGraph"><em>FlameGraph Repository</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*NSVyJ_Mzj0s7ddM7044xXQ.png" /><figcaption><strong>UML Diagram of Process Flow</strong></figcaption></figure><p><em>Source: Wikimedia</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*ihti5O0ydBn0J8RSUBC4nA.png" /><figcaption><strong>UML Data Structure</strong></figcaption></figure><p>Other times, I’ll stop at a breakpoint smack dab in the middle of an important function, and work my way through the stack to understand how I got there. If you decide to manually follow the code, make sure your editor is setup to let you use “go to definition” and “find all references” for quick navigation.</p><p>For data structures, review the data types and when key variables are being set. Use the debugger to interrogate these data structures at critical moments.</p><p>In addition to integration tests, <a href="https://twitter.com/marccataford/status/1108059456603066368">reviewing important pull requests</a> are a powerful way to approach a new code base. PRs often are easier to understand, as they encapsulate an isolated feature. PRs also provide the narrative background beyond the why and how of a code addition.</p><p>During these deep dives, I keep two markdown docs open. The first is a “level up my coding” doc where I list out new syntax I’m seeing and code patterns I find interesting for my own learning (others call this a <a href="https://news.ycombinator.com/item?id=9786011">glossary</a>). The second is a doc that lists out key questions I have for the developers of the codebase. At this stage, I also add to the documentation when I notice gaps.</p><p>Deep dives are especially powerful in pairs with someone who knows the code. If I have limited time with a developer on the project, I always have them trace me through a few key flows. Once I have a basic understanding of a few key flows, it’s much easier to dig in on my own.</p><h4>4. Write Code</h4><p>Unlike literature, where reading and writing are separate endeavors, a critical part of “reading” code is actually writing code. Without writing code, it’s nearly impossible to internalize a code base. The two easy approaches to start are to write tests and address simple features/bugs.</p><p>Writing tests is an active form of reading, forcing you to pay attention to the actual inputs and outputs of a particular interaction. Writing tests imprints the code in your memory in a way that reading alone cannot.</p><p>For me, unit tests are an easy way to start. Once I have some base mastery, I move over to integration tests that force me to understand increasingly larger parts of the codebase. Sometimes I’ll even rewrite an existing integration test, to test my understanding of how a critical call works.</p><p>The other easy approach is to write simple features or address easy bugs. Both of these tasks don’t demand complete knowledge of the codebase, but still force you to confront the code. Contributing bug fixes and documentation is also an easy way to give back to your dependencies.</p><p>These methods provide quick wins, when you need it most. By augmenting RSDW with a few broader lessons, reading code will become less daunting.</p><h4>Some tips for reading</h4><p>The RSDW process is not dogmatic. Inevitably, engineers figure out the personal ways they like to dig into a new code base (the process also varies dramatically based on language, the tooling available, and the type of code base in front of you).</p><p>Despite that, the RSDW process does argue for a systematic approach when you’re seeing new code. It also encourages active introspection into the code, be it writing tests or actively using a debugger to interrogate data structures. The process of reading code is far different than the more passive process of reading books.</p><p>You’ll also find reading new code is exhausting. You are intricately retracing code flows and trying to concurrently hold tens of new data structures and functions in your head. Be aggressive about taking breaks when you’re approaching a new code base. When I’m starting on a new codebase, a few good hours of a day of reading is all I need to feel productive.</p><p>While it’s critical to develop good reading skills, it’s just as important to be thoughtful about what you read.</p><h4>What code should you read?</h4><p>Early in your career, I believe that 60% of your time should be spent reading code. Maybe a third of that should be code outside of the direct codebases you actually build on. That’s an awfully large amount of time to fill, so what should you read?</p><p>The easiest way to get started reading, and the highest ROI, is to learn your dependencies. Internalizing how your dependencies work lets you more easily debug and reason across your entire system.</p><p>The other high ROI path is to pick an important system at your company that you interface with, and read through it. Not only will this be valuable in your work, but professional codebases are different from open source codebases.</p><p>Beyond the direct systems you interact with, cultivate an openness to reading widely. Early on in my career, I recommend putting aside an hour in the morning or evening to read through code outside your day to day work. It sounds painful after a hard day of work, but pick a codebase you’re excited to dig into and try it for a week.</p><p>For example, <a href="https://github.com/antirez/redis">Redis</a> is known as a popular starting point in C. For less readable, more complex codebases an easy way to start is to read a specific subsystem.</p><p>Side projects are a powerful way to read, because they force you to learn a different world. You’ll need to read new dependencies and explore different codebases for what you’re building. Though it doesn’t seem like reading, it’s a project that forces you to actively read what you’ll be using.</p><p>Outside work, you should read tools widely different from your day job. If you’re used to high level abstractions, learn an abstraction level (or three) down. If you work in one language, pick another language to read in your free time. If you consistently have to think about one constraint (e.g., the time for next screen refresh in graphics programming), find another constraint (e.g., saving battery life in mobile programming).</p><p>Another good approach to reading code is to read and rewrite coders you respect. Where a young Didion wrote Hemingway or Hunter Thompson <a href="http://www.openculture.com/2017/06/hunter-s-thompson-typed-out-the-great-gatsby-farewell-to-arms.html">typed out the Great Gatsby</a>, write out antirez’s or gaearon’s or mrdoob’s code starting with a simple library. Read their other codebases. Stay up to date of their most recent work.</p><p>Stephen King cautioned writers that “if you don’t have time to read, you don’t have the time (or the tools) to write. Simple as that.” Similarly, for software engineers, writing fresh code may be the most fun, but (actively) reading code is what will separate you from the pack.</p><p><em>This is a post in my occasional series, </em><a href="https://www.nemil.com/on-software-engineering/index.html"><em>Notes to Young Software Engineer</em></a><em>. Sign up </em><a href="http://eepurl.com/cxs5Zr"><em>here</em></a><em> or </em><a href="https://www.nemil.com/feed.xml"><em>follow the RSS feed</em></a><em>. All pieces in this series are published as drafts, with relevant community feedback incorporated. Thanks to </em><a href="https://brandur.org"><em>Brandur Leach</em></a><em>, </em><a href="https://twitter.com/jakecraige?lang=en"><em>Jake Craige</em></a><em>, and </em><a href="https://twitter.com/bstodghill2?lang=en"><em>Breck Stodghill</em></a><em> for reflections and feedback.</em></p><h4>Links</h4><h4>Articles on reading code</h4><ul><li><a href="https://news.ycombinator.com/item?id=9784008">Ask Hacker News: How do you familiarize yourself with a new codebase</a></li><li><a href="https://news.ycombinator.com/item?id=16299125">Ask Hacker News: How to understand the large codebase of an open-source project?</a></li><li><a href="https://news.ycombinator.com/item?id=8263402">Strategies to quickly become productive in an unfamiliar codebase</a></li><li><a href="https://stackoverflow.com/questions/215076/whats-the-best-way-to-become-familiar-with-a-large-codebase">What’s the best way to become familiar with a large codebase?</a></li><li><a href="http://wiki.c2.com/?TipsForReadingCode">Tips for Reading Code</a></li><li><a href="http://www.se-radio.net/2009/11/episode-148-software-archaeology-with-dave-thomas/">Software Engineering Radio: Software Archaeology with Dave Thomas</a> (Podcast)</li></ul><h4>Books</h4><ul><li><a href="https://en.m.wikipedia.org/wiki/Code_Reading">Code Reading: The Open Source Perspective</a> (book)</li><li><a href="https://www.amazon.com/Working-Effectively-Legacy-Michael-Feathers/dp/0131177052">Working Effectively with Legacy Code</a> (book)</li></ul><h4>Codebases to read</h4><ul><li><a href="https://news.ycombinator.com/item?id=9896369">Good Python codebases to read</a></li><li><a href="https://news.ycombinator.com/item?id=14462125">Good Go codebases to read</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=467e31f243b0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/one-secret-to-becoming-a-great-software-engineer-read-code-467e31f243b0">One secret to becoming a great software engineer: read code</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Engineering Mistakes That Kill Startups]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@nemild/four-startup-engineering-killers-1fb5c498391d?source=rss-544d9b0e147e------2"><img src="https://cdn-images-1.medium.com/max/700/1*bgeNz76pgL19vrP5Erv9gQ.jpeg" width="700"></a></p><p class="medium-feed-snippet">From chasing shiny tech to scaling too soon, beware these common missteps</p><p class="medium-feed-link"><a href="https://medium.com/@nemild/four-startup-engineering-killers-1fb5c498391d?source=rss-544d9b0e147e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@nemild/four-startup-engineering-killers-1fb5c498391d?source=rss-544d9b0e147e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fb5c498391d</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering-killers]]></category>
            <category><![CDATA[hackernoon-top-story]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Nemil Dalal]]></dc:creator>
            <pubDate>Tue, 19 Feb 2019 13:16:21 GMT</pubDate>
            <atom:updated>2019-08-20T19:12:44.170Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to Hack an Engineer]]></title>
            <link>https://medium.com/hackernoon/how-to-hack-an-engineer-7f2c6b9c6382?source=rss-544d9b0e147e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f2c6b9c6382</guid>
            <category><![CDATA[social-engineering]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[hack-an-engineer]]></category>
            <dc:creator><![CDATA[Nemil Dalal]]></dc:creator>
            <pubDate>Tue, 17 Apr 2018 14:16:01 GMT</pubDate>
            <atom:updated>2018-04-17T14:16:01.544Z</atom:updated>
            <content:encoded><![CDATA[<h4>As engineers, we widely discuss exploits on the technology systems we manage. It’s time to do the same for exploits of our personal information sources.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*XQzW3MkIVb2Rd4F5TMDZHA.png" /><figcaption><a href="http://eepurl.com/cxs5Zr">Get this as a free sticker</a></figcaption></figure><p>In 2015, I found myself talking to a smart entrepreneur who had just raised millions of dollars in venture capital from a prominent venture capital (VC) firm. He was flying high after getting substantial press and recruiting a number of early employees. His business also wholly depended on a popular open source project.</p><p>As part of his strategy, the CEO gave a core open source developer in the project equity. With this, he boasted that he would get critical information sooner, influence the roadmap for his company’s benefit, and recruit developers from the project to his company</p><p>I was doubtful this connection would ever be publicized by the open source developer. Would he speak glowingly about the company at a conference, despite private reservations? How would he influence the decisions of his fellow developers? Would developers early in their career follow his missives without adequate reflection?</p><p>Computer engineers regularly deal with <a href="https://en.wikipedia.org/wiki/Exploit_(computer_security)">exploits</a> on their technical systems, where an external party takes advantage of a bug or vulnerability. An “exploit” or social engineering of our personal information sources — motivated parties influencing subreddits, conferences, meetups, blogs, journalists, professors, industry analysts — should be perceived similarly. As this example shows, even your peers can be influenced.</p><p>As engineers, it’s valuable to develop the antibodies that enable us to make the best decisions — both for our teams and for our own careers — despite the desires of these motivated parties. Beyond identifying ways we can be influenced, I list out three techniques to help us make better decisions.</p><blockquote>I’ve created a <a href="https://github.com/nemild/hacking-engineers">Github repo</a> listing the some inputs for startup engineering decisions. For each, I’ve noted how they work — and how they can be exploited.</blockquote><h3>The War to Influence Engineers</h3><p>This is just one example in a larger war that rages in this global era of computing: that for the hearts of engineers in technology.</p><p>Some of the many groups that will try to shape our views include:</p><ul><li><em>Developer tools teams</em> who want to sell their technology or grow their platform</li><li><em>Companies</em> who wants to hire us</li><li><em>Open source developers</em> who want to recruit contributors and users</li><li><em>Venture capitalists</em> who want to fund us</li><li><em>Training programs</em> that want to sell their courses</li><li><em>Consulting firms</em> that want us to hire them</li><li><em>Social networks</em> that are trying to maximize engagement, readership, and revenue</li></ul><p>The content they create and sponsor (press releases, meetups, blog posts, conferences, speaker talks) play a critical role in the decisions we make — from the technology we adopt to the companies we join.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*2vAbJz_awpcDx7Mhzyp_Wg.png" /></figure><p>A press release indicating large traction (often with many missing numbers) may be a primary reason to join a startup. A blog post or popular talk on the latest database technology — like NoSQL — may be a reason to experiment and later switch. A college lecturer may partly be there to pitch their own company’s technology. The most upvoted Hacker News (HN) posts over a year may influence what technologies we choose to adopt. And yet, as consumers of this information, many of us don’t always critically examine the information and its source.</p><p>In startups, bad technology choices made based on these inputs can divert the focus, putting the mission at risk. For an individual engineer, learning the wrong technology can waste our time. Joining the wrong company that sells us false promises can set our career back.</p><blockquote><strong>Case Study: Dev Tool Marketing at MongoDB</strong></blockquote><blockquote>MongoDB was one of the fastest growing NoSQL databases in the late 2000s that promised a “modern” database experience.</blockquote><blockquote>In <a href="https://www.nemil.com/mongo/3.html">my deep dive into the early marketing strategy behind MongoDB</a>, I pointed out issues relevant in dev tools marketing including:</blockquote><blockquote>- Speakers invited to many MongoDB meetups/conferences would have their own motivations (trying to sell their consulting services, marketing for their own dev tools products)</blockquote><blockquote>- Hack academies and early programmer blogs were valuable allies for pitching the MEAN stack, while not seeming like a sales pitch when seen on HN/Reddit</blockquote><blockquote>- MongoDB would argue that nearly every use case should be solved with their database, without highlighting the tradeoffs in different use cases</blockquote><blockquote>- College hackathons were a way to influence early developers who may not have fully understood the tradeoffs they were making</blockquote><p>Even though I point out the issues in this case study, I am far from a dispassionate scientist when on a mission for my team. Given that, it’s at least important to ensure that all engineers have the general tools to understand some of the messages we see. And in this era of fake news, <a href="https://qz.com/1130094/todays-biggest-threat-to-democracy-isnt-fake-news-its-selective-facts/">selective facts</a>, and troll armies, these lessons can also help us assess information far beyond engineering content.</p><h3>Hidden Influences</h3><p>Unlike previous generations of marketing, the external influences in engineering media today are often disguised.</p><p>The purpose of a press release or a sales call is clear. When this content is used to give a talk at a conference or inspire someone else to write a blog post, they blur the line. With a powerful marketing budget or fundraise, it becomes increasingly easy to publicize and convince others with one’s message, regardless of the veracity.</p><p>In Silicon Valley, well placed friends tell me that they shudder at the information sources available to most — and how uncritically different messages are internalized. I worry especially about junior engineers (such as those in college and on <a href="https://www.reddit.com/r/learnprogramming">r/learnprogramming</a>) and those far from top tech centers, who may not realize how “the sausage is made.”</p><blockquote><strong>Case Study: Training Programs</strong></blockquote><blockquote>Free Code Camp, a popular developer blog with 350k followers, carried a recent post that argued REST is dead and GraphQL is the future (“<a href="https://news.ycombinator.com/item?id=14839576">REST in Peace. Long Live GraphQL</a>”). The article had been posted by the head of Free Code Camp and written by an author who was concurrently selling a GraphQL training program (my critique <a href="https://news.ycombinator.com/item?id=14840321">here</a>).</blockquote><blockquote>Reflecting back on my own early days, I worry about junior engineers who might feel like they have to learn GraphQL based on an article like this rather than realizing all the conflicts involved. An older example from them is “<a href="https://medium.freecodecamp.org/the-real-reason-to-learn-the-mean-stack-employability-29011ff6b2eb">The Real Reason to learn the MEAN stack: Employability</a>” — which many of my most thoughtful friends would have strenuously disagreed with. I especially worry about what content like this does in early developer communities, where there many not be enough thoughtful engineers to disagree with these viewpoints.</blockquote><blockquote>Beyond direct influence, a surprising percentage of posts on engineering social media are content marketing. These posts aim to add value — but are written for the primary purpose of helping their companies sell their product. Readers can sometimes internalize them as “journalism,” even though their objective is to make a sale, influence a mindset shift, or improve SEO.</blockquote><blockquote><strong>Case Study: Content Marketing</strong></blockquote><blockquote>Union Square’s Fred Wilson <a href="http://avc.com/2016/08/understanding-vcs/">notes how pervasive content marketing is in tech</a> and encourages critical assessment of the message (emphasis added):</blockquote><blockquote><em>So how should entrepreneurs use this knowledge that is being imparted by VCs [like myself] …? Well first and foremost, you should see it as content marketing…</em></blockquote><blockquote><em>That doesn’t mean it isn’t useful or insightful. It may well be. But you should understand the business model supporting all of this free content. </em>It is being generated to get you to come visit that VC and offer them to participate in your Seed or Series A round.<em> That blog post that Joe claimed is not scripture in his tweet is actually an </em>advertisement<em>. Kind of the opposite of scripture, right?</em></blockquote><p>For all these reasons and more, my most thoughtful friends use their own networks to understand reality instead: college/graduate school friends from select universities, frank talks with portfolio CEOs (for investors), ‘off the record’ conversations with connections at the various platform providers, trenchant blogs from front line engineers. Their information sources are less influenced by self-interest, providing a more objective view of the world. People can also say things privately they wouldn’t feel comfortable sharing broadly.</p><p>These friends of mine also have a deep-seated desire (specifically, a financial or technical motivation) to get at the truth, and so aim to understand the incentives driving every one of their sources. Though they may be outwardly agreeable, internally they’re deeply critical thinkers.</p><h3>How Engineers Can Make Better Choices</h3><p>These issues have a basic lesson: nothing is a replacement for surrounding oneself with primary sources, a community interested in the truth, and thoughtful engineers.</p><blockquote>For more, see my <a href="https://github.com/nemild/hack-an-engineer">Hack an Engineer Github Repo</a></blockquote><p>Beyond the self-interested factors, engineering media can be distorted for other reasons. For example, each upvote on Hacker News is equal — meaning that the world’s most thoughtful expert on a topic has the same voting power as someone inexperienced. Nearly every social media algorithm favors engagement over any other metric, meaning that what we read is simply a function of what those around us want to read (this echoes <a href="https://www.nemil.com/s/part3-horror-films.html">my research on what types of deaths are covered in a leading US newspaper</a>).</p><blockquote><strong><em>Case Study: Cryptocurrency tribes and social media</em></strong></blockquote><blockquote>In social media, the group you surround yourself by can shape your attitudes, even though engineering decisions should be based on empiricism and facts. Social media groups and algorithms pick content that confirms its users’ beliefs — and paint the opposite side in the worst light. This tribalism can be regularly seen in cryptocurrency subreddits, meaning that readers consume a distorted reality (see also <a href="https://en.wikipedia.org/wiki/Filter_bubble">filter bubbles</a>).</blockquote><blockquote>As the cofounder of Coinbase, Fred Ehrsam, <a href="https://twitter.com/FEhrsam/status/892429946550837248">explains</a>:</blockquote><blockquote><em>“Cryptocurrencies create strong tribalism. Once you own a currency, your incentives are to make that currency go up in value. Crypto tribalism can be seen on reddit every day. Subreddits generate and report news that support their holdings.</em></blockquote><blockquote><em>Crypto tribalism plays out in two common ways: 1) people promoting their own currency and 2) people discrediting other currencies. People promoting their own currency is evidenced by the imbalance of positive to negative news about a currency on its own subreddit.”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/249/1*JK6FD07jOf2GXYwAXaIHAg.png" /><figcaption><a href="http://eepurl.com/cxs5Zr">Get a free sticker</a></figcaption></figure><p>For now, I’ll suggest three simple points that go far in assessing engineering media:</p><h4>1. Identify incentives behind content that informs important decisions</h4><p>First, consider a writer/speaker’s motivation — both directly (an employee or investor in the company) or indirectly (a public speaker who is a consultant looking for a gig or employee looking for a job/advisorship).</p><p>When I read a post or hear a speaker, I often ask myself a few questions:</p><ul><li><strong>Background</strong>: What is their technical background and why are they well suited to speak on this topic?</li><li><strong>Objectives</strong>: What are their personal objectives in speaking/blogging? (e.g., recruiting, personal brand, new business); there almost always is one</li><li><strong>Conflicts</strong>: What conflicts might they have and how does this influence the message?</li><li><strong>Allies</strong>: Who else wants this content out there?</li><li><strong>Distributor Incentives</strong>; Why is the distributor (social network, media publication) putting this content in front of me? (who are the upvoters, what is the business model, etc.)</li></ul><p>When we see a lot of press from a company, it’s often a sign that they want something from us. Their employees have consciously spent the time to sit down with a journalist or taken the time to write a post.</p><h4>2. Debunk claims</h4><p>Second, inculcate a desire to debunk claims.</p><p>For example, companies regularly trumpet their (tailor-made) benchmarks that show their products in the best light. It’s often not that difficult to run our own benchmarks that reflect our real world use cases.</p><p>The direct reading of codebases is a powerful corrective (where available). It’s a primary source that doesn’t have ‘spin’ built in.</p><p>Looking back on trends in technology and where they ended up is another approach, which is akin to backtesting: it’s easier to tune out hype, when we think about how people in a few years may perceive it, based on things we’ve seen in the past.</p><p>Say something in online communities when you disagree or see egregious incentive issues (here’s <a href="https://news.ycombinator.com/item?id=16320022">one favorite recent example on AV1 vs HEVC</a>). On HN, this could be comments or a post of your own, even if it’s with a throwaway account. New social network designs might let us award karma to people who list out the key incentive issues in the future.</p><h4>3. Build a community of respected peers and thoughtful experts</h4><p>Third, examine the community that you lean on to determine important technical decisions.</p><p>It’s important to have a community of people who benefit from the truth, think critically, and have content expertise. This could be former employees, classmates, or your coworkers. You can augment this with the most thoughtful engineers you can find. Online, you can often find some of these groups in the comments of niche HN posts and open source mailing lists/chat rooms. In your early years, finding a thoughtful mentor is critical.</p><p>In many ways, this approach mirrors the <a href="https://en.wikipedia.org/wiki/Web_of_trust">web of trust</a> in computer security, where we look to trusted friends — and people these trusted friends are connected to.</p><p>This point underlines the benefits of a thoughtful engineering curriculum taught by dispassionate teachers. I’m unaware of any school who teaches early engineers how they should best consume engineering media — or how to choose a technical tool. Often, this means that we’re then vulnerable for a few years, until we’ve incorporated the lessons from working on a good team.</p><p>Having a few thoughtful experts in our community is also critical when assessing deeply technical decisions like what database to use or how best to architect a system. The danger with some experts — the non-thoughtful variety — is that their confidence in their abilities means they don’t question many deep seated assumptions and can’t make adjustments when the world changes. Thoughtful experts have both content expertise and <a href="https://blog.codinghorror.com/strong-opinions-weakly-held/">strong opinions that are weakly held</a>.</p><h3>Coda</h3><p>We engineers share some similarities with the machine learning algorithms we design. In both, data is used to make inferences about future decisions. As such, it’s important to have a thoughtfully curated training data set — and to adjust for any errors when our engineering inputs are compromised.</p><p>I’ve hardly touched on all the other questions we should be discussing, beyond encouraging critical thinking and finding trusted networks of thoughtful engineers. For example, should we debate alternate Hacker News and Twitter algorithms with the hope of creating better engineers? Should there be conflict disclosures for open source developers? Should popular engineering blogs such as <a href="https://www.freecodecamp.org/">Free Code Camp</a> have a board of engineers who technically assess content and the background of writers? Should we teach engineering media literacy in bootcamps and CS programs?</p><p>Still, I’m encouraged by the fact that critical thinking and testing hypothesis is such a natural part of how engineers and scientists approach the world. This mindset has a critical role to play far beyond the day to day engineering problems we aim to solve.</p><p><em>Originally published at </em><a href="https://www.nemil.com/musings/hack-an-engineer.html"><em>www.nemil.com</em></a><em>. Get a free sticker and sign up for my mailing list </em><a href="http://eepurl.com/cxs5Zr"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f2c6b9c6382" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-hack-an-engineer-7f2c6b9c6382">How to Hack an Engineer</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>