<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Vineet Thanedar</title>
    <description>The latest articles on DEV Community by Vineet Thanedar (@vinthanedar).</description>
    <link>https://dev.to/vinthanedar</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F130277%2F3e01841f-9534-49c6-9132-5395758ed082.jpg</url>
      <title>DEV Community: Vineet Thanedar</title>
      <link>https://dev.to/vinthanedar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vinthanedar"/>
    <language>en</language>
    <item>
      <title>Be The One Who Ships</title>
      <dc:creator>Vineet Thanedar</dc:creator>
      <pubDate>Sun, 20 Jan 2019 18:38:54 +0000</pubDate>
      <link>https://dev.to/vinthanedar/be-the-one-who-ships-1hcj</link>
      <guid>https://dev.to/vinthanedar/be-the-one-who-ships-1hcj</guid>
      <description>&lt;p&gt;As hackers, engineers, entrepreneurs, and side-project doers, we tend to be perfectionists. We care about the work product we put out there, and want to make sure we showcase our best work.&lt;/p&gt;

&lt;p&gt;However, most of us likely have half-done (abandoned) projects, ideas we have that never seem to get off the ground, or projects that move so slowly that we might as well have never started. I've been there numerous times myself.&lt;/p&gt;

&lt;p&gt;It's not that we can't quite see the problem - perfection is the enemy of good enough. This is especially true when there are time and resource constraints.&lt;/p&gt;

&lt;p&gt;I documented some of what we did right and pitfalls we avoided in the past year and a half of shipping product at my startup.&lt;/p&gt;

&lt;p&gt;You may relate to these, and I hope you catch yourself the next time you find yourself committing one of these (unforced) errors, and course correct your way to &lt;em&gt;done&lt;/em&gt; sooner.&lt;/p&gt;

&lt;p&gt;I originally posted this to my personal blog here - &lt;a href="https://vinthanedar.com/2019/01/17/teams-that-ship/"&gt;https://vinthanedar.com/2019/01/17/teams-that-ship/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hope you enjoy reading it and would love to hear about your experiences!&lt;/p&gt;

&lt;p&gt;tl;dr&lt;/p&gt;

&lt;p&gt;Whether it's a side project, or building software at your company:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Build and preserve momentum like your life depends on it&lt;/strong&gt;&lt;br&gt;
&lt;em&gt;Keep moving forward one bit at time, no matter how minor the step may be.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Progress &amp;gt; Polish&lt;/strong&gt; &lt;br&gt;
&lt;em&gt;It is a vastly better approach to circle back to make something better, but after having gone to battle with it.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Be your own customer&lt;/strong&gt;&lt;br&gt;
&lt;em&gt;Dog-food your product to enable faster progress.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Beware of rabbit-holes. They are the plague.&lt;/strong&gt; &lt;br&gt;
&lt;em&gt;Be ruthless in doing things that need to be done, not the things you want to do.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>startup</category>
      <category>learning</category>
      <category>products</category>
      <category>software</category>
    </item>
  </channel>
</rss>
