<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Email on Yutong Jin</title><link>https://yutongjin.com/tags/email/</link><description>Recent content in Email on Yutong Jin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://yutongjin.com/tags/email/index.xml" rel="self" type="application/rss+xml"/><item><title>Practice 4-10</title><link>https://yutongjin.com/posts/410_learning/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://yutongjin.com/posts/410_learning/</guid><description>&lt;h1 id="lessons-learned-from-my-product-discovery-journey"&gt;Lessons Learned from My Product Discovery Journey&lt;/h1&gt;
&lt;h2 id="key-lessons"&gt;Key Lessons&lt;/h2&gt;
&lt;h3 id="1-start-with-a-minimal-product-scope"&gt;1. Start with a minimal product scope&lt;/h3&gt;
&lt;p&gt;I learned that I should begin with a small and clear set of functional requirements instead of adding extra features too early. In system design interviews, simple is usually better than broad. I should focus first on the core user needs and avoid introducing features that are not explicitly required.&lt;/p&gt;
&lt;h3 id="2-always-call-out-non-functional-requirements-early"&gt;2. Always call out non-functional requirements early&lt;/h3&gt;
&lt;p&gt;One of my biggest takeaways is that I need to explicitly mention non-functional requirements such as:&lt;/p&gt;</description></item></channel></rss>