<?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: Ian Ito</title>
    <description>The latest articles on DEV Community by Ian Ito (@ian808).</description>
    <link>https://dev.to/ian808</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%2F1426554%2Feefaf1a6-7a26-44cb-ae7c-c3083252d28d.jpeg</url>
      <title>DEV Community: Ian Ito</title>
      <link>https://dev.to/ian808</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ian808"/>
    <language>en</language>
    <item>
      <title>Replacing the internal tooling we used at Meta (Facebook)</title>
      <dc:creator>Ian Ito</dc:creator>
      <pubDate>Wed, 05 Jun 2024 15:42:47 +0000</pubDate>
      <link>https://dev.to/ian808/replacing-the-internal-tooling-we-used-at-meta-facebook-5hh8</link>
      <guid>https://dev.to/ian808/replacing-the-internal-tooling-we-used-at-meta-facebook-5hh8</guid>
      <description>&lt;h2&gt;
  
  
  A common startup dilemma
&lt;/h2&gt;

&lt;p&gt;As an early-stage startup, you can afford to spend time building things that are not core to your product.&lt;/p&gt;

&lt;p&gt;This might be controversial, but my experience has been to pick and choose the battles you want to face.&lt;/p&gt;

&lt;p&gt;While all startups are different, we eventually encounter a common dilemma: "Do you buy a solution or build one yourself?"&lt;/p&gt;

&lt;p&gt;Some startup teams opt for the scrappy approach, building in-house tools/ finding an open-source solution, while others default to buying a SaaS vendor.&lt;/p&gt;

&lt;p&gt;Statsig was no different. However, since the founding engineering team were all ex-Meta (Facebook), they looked to replace the tooling they used before.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sharing your tech stack is cool, but sharing your story is more helpful
&lt;/h2&gt;

&lt;p&gt;The biggest takeaway for me while sharing their story is that posts about your tech stack might be cool on social, but they leave out the most important part: how you arrived there. What battles did you face and what tradeoffs did you make trying different tools?&lt;/p&gt;

&lt;p&gt;Below is a full breakdown of Statsig's tooling &amp;amp; tech stack, and we wrote about the struggles we faced along the way to get there.&lt;/p&gt;

&lt;p&gt;(...My favorite story is how we tried to save money by using an open-source Notion alternative. Yeah, that didn't work out.)&lt;/p&gt;

&lt;p&gt;If you're curious, we wrote about &lt;a href="https://scalingdown.substack.com/p/when-you-miss-the-tools-you-used"&gt;our story here&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  A peek into an ex-meta tech stack
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3hsuri2ocuwywzh2tqm3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3hsuri2ocuwywzh2tqm3.png" alt="A peek into our tech stack" width="800" height="978"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Let me know which tools you replaced and with what. Would love to hear how you solved your startup dilemma.&lt;/p&gt;

</description>
      <category>startup</category>
      <category>tooling</category>
    </item>
    <item>
      <title>Hello (Dev) world</title>
      <dc:creator>Ian Ito</dc:creator>
      <pubDate>Sun, 02 Jun 2024 21:04:38 +0000</pubDate>
      <link>https://dev.to/ian808/hello-dev-world-42ab</link>
      <guid>https://dev.to/ian808/hello-dev-world-42ab</guid>
      <description>&lt;p&gt;Hey, Dev community 👋 – Ian here.&lt;/p&gt;

&lt;p&gt;Thought I'd share a quick intro about myself:&lt;/p&gt;

&lt;p&gt;I'm an avid reader, writer, and indie hacker. However, most of my startup ideas are now buried in my virtual backyard, but at least I'm learning (my attempt at justifying the sunk cost 🤷🏻‍♂️).&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;I'm a curator of tech newsletters and often share what I've been reading&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;I'm an editor of a Substack called Scaling Down – a starter guide for engineers and product teams who made the leap from Big Tech to a startup&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;– I build web scrapers to help me aggregate information and tinker with RAG-based web apps to help me summarize it&lt;/p&gt;

&lt;p&gt;Happy to help with any of the above.&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
