<?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 Jingwei Hao on Medium]]></title>
        <description><![CDATA[Stories by Jingwei Hao on Medium]]></description>
        <link>https://medium.com/@jwhao?source=rss-12d33c76c331------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5QV3dthFW3rtuy4yFXLREA.jpeg</url>
            <title>Stories by Jingwei Hao on Medium</title>
            <link>https://medium.com/@jwhao?source=rss-12d33c76c331------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:53:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jwhao/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[Feelings]]></title>
            <link>https://medium.com/@jwhao/feelings-523da8c0614c?source=rss-12d33c76c331------2</link>
            <guid isPermaLink="false">https://medium.com/p/523da8c0614c</guid>
            <dc:creator><![CDATA[Jingwei Hao]]></dc:creator>
            <pubDate>Fri, 25 Aug 2023 05:22:12 GMT</pubDate>
            <atom:updated>2023-08-25T05:34:30.930Z</atom:updated>
            <content:encoded><![CDATA[<p>I work in software engineering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*xLHEXbOPe5zUyovzwglqVA.png" /></figure><p>In engineering, depending on the culture or team you are in, usually, feelings (or emotions) are not considered important, or even, sometimes, they are considered “something that’s nonexistent”, because “everyone is supposed to speak from logic and reasons” in engineering.</p><p>I used to think in this way too. I believed everything I thought and reasoned came from logic and rationale. Until I read <a href="https://www.goodreads.com/book/show/26329.Emotional_Intelligence">Emotional Intelligence by Daniel Goleman</a>. The book introduced an important concept to me: <a href="https://en.wikipedia.org/wiki/Emotional_literacy">Emotional Literacy</a>. The book also mentioned, professionals working in certain fields tend to have less awareness of their own emotions, let alone the emotions of others; engineering is unsurprisingly one of these fields.</p><p>This understanding opened a new world for me.</p><p>I realized, at that time, I was emotionally illiterate.</p><p>I also got to know another concept related to emotional illiteracy: <a href="https://en.wikipedia.org/wiki/Somatization">Somatization</a>. For individuals who do not have a good sense of how they feel moment by moment, feelings or emotions tend to solidify in their muscles and nervous systems and then manifest as pains or tensions (heaviness) in muscles.</p><p>Later on (Spring of 2019) I started practicing <a href="https://en.wikipedia.org/wiki/Vipassan%C4%81">Vipassana meditation</a>. I could finally agree and tell from my own meditation practice: we (humans) are fundamentally emotional beings:</p><p><strong>Every single thought and action </strong>comes from emotion(s)/feeling(s).</p><p>When we feel great, meaning on the subtlest level, most of the tiny little sensations we feel (which usually don’t registered by our conscious mind when we are going through our daily activities) at the moment are good, our thoughts are more positive. When we feel bad, negative thoughts surface and occupy our conscious mind.</p><p>To put it in another way: emotions and feelings are the fundamental driving force behind <strong>every single thought and action</strong> of ours.</p><p>We are programmed to chase the good feelings and avoid the bad ones. And every moment of our existence, there are millions of subtle feelings arising and passing away within our body, they affect our thoughts and actions in the way most of us never realize.</p><p>After knowing this from my own meditation experience, asking myself the question, “why am I doing what I’m doing? What emotion am I experiencing right now” becomes a habit for me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=523da8c0614c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Vipassana Story (so far)]]></title>
            <link>https://medium.com/@jwhao/my-vipassana-story-so-far-ecfe9795967e?source=rss-12d33c76c331------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecfe9795967e</guid>
            <category><![CDATA[vipassana]]></category>
            <category><![CDATA[wisdom]]></category>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Jingwei Hao]]></dc:creator>
            <pubDate>Fri, 15 Apr 2022 01:52:40 GMT</pubDate>
            <atom:updated>2022-04-15T02:03:34.512Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been through the 10-day Vipassana meditation course twice and served the 10-day course once in the past three years. Here are my takes.</p><p><strong>How did I decide to go in the first place?</strong></p><p>If you haven’t heard about it, during a 10-day Vipassana meditation course, you stay silent for the first nine days, which means you are not supposed to speak, there’s no phone, no internet, no books, you are also not supposed to use your body languages to communicate with your fellow mediators. The days start at 4:30 am with a 1.5 hours meditation and end at 9 pm after the last meditation of the day.</p><p>“It sounds pretty crazy” was my thought the first time when I heard about Vipassana. It also sounded interesting because, if it was not, why did people go there and do it? But still, it felt intense, so I placed it on the list of things I keep on my mind that sound interesting, but I’m not motivated enough to try yet.</p><p>After another year or so, I read the book <a href="https://www.goodreads.com/book/show/18693771-the-body-keeps-the-score">The Body Keeps the Score: Brain, Mind, and Body in the Healing of Trauma</a>. This book is one of the most impactful books in psychology recently. I’m not going to spoil the book for you, and this is a post talking about Vipassana instead of personal traumas, so I’m not going to start introducing this book, but if you are generally interested in becoming a happier person, you should read it. The author mentioned a meditation practice in the book: focus your attention on a chronicle pain you have, observe it without any judgment or intention. I tried this mediation for about 15 minutes on my stomach, and a memory from my kindergarten surfaced. I was about 3-year old and was verbally abused by a teacher there. I wasn’t able to effectively communicate with my parents about it. I was three and didn’t know how to express complex emotions yet. From the surfaced memory and related thoughts, I could tell that the world had been grayed out a little for me. You know how big of an impact it is when a 3-year-old just decided the world is a little bit grayer from now on. And I carried that grayer view through my adult life until this 15 minutes meditation. If anyone approached me about this incident before the meditation, I wouldn’t recall it. It was a traumatic experience, and my brain suppressed it.</p><p>That’s when I decided to give Vipassana a try.</p><p><strong>Why did I do my first course at the closest center to me?</strong></p><p>When I decided to try out Vipassana for the first time, before COVID, travel was still available. There are more than 200 Vipassana meditation centers in the world. All the courses are free, and the teachers don’t get paid. Actually, no one gets paid. Knowing that, I was thinking about traveling to Japan or Thailand for my first course, there will be yummy local food, I thought. Then, the second thought: what if I couldn’t bear to stay there for ten days and I needed to leave early? If I’m in a foreign country, I’d have to find lodging when I leave the center. So I decided to go to the closest center to me; in the worst case, I’ll ask for my car key back and drive home.</p><p>It was proven to be a good idea. During my first course, there were a few times when I wanted to drop out; knowing that this was an option helped me decide to stay.</p><p><strong>Serving</strong></p><p>As mentioned earlier, all the courses are free, purely running on donation, and no one gets paid. So then, who prepares the food?</p><p>Servers.</p><p>Servers are Vipassana meditators who had gone through the 10-day course and decided to come back and serve the course so others could get the benefit of the meditation and getting through the course.</p><p>I signed up for serving with a little bit less noble goal :)</p><p>It was May 2021, about two years after my first 10-day course, and the world was still in lockdowns, pandemics, bad news, etc. I was affected and very burnt out. I know the meditation centers were closed, but one day I noticed that the center closest to me got re-opened, and the most recent 10-day course that still had availabilities was for servers only. So I signed up to be a server, knowing that being a server, one still will be meditating for 3 hours per day, and I will be in a peaceful, calm, and kind environment.</p><p>It was the best decision.</p><p>We had a small group of servers during the ten days, about 6 of us. We bonded well. It felt like cooking, baking, and hanging out with your best friends in the kitchen all day. Don’t get me wrong, the physical work was extremely exhausting, but I was always in good spirit. It was also the biggest dose of pure love I ever received. It was the first time I had a tangible experience of how it felt to be kindly loved by so many individuals from different backgrounds. I am very grateful that it happened. I am very grateful to everyone on the servers team. We enjoyed each other’s accompany a lot, and we still hang out with each other from time to time.</p><p>This experience gave me one great insight: pure love (compassion or loving-kindness) is a gift. It drives fear away. And impossibles become possible when there’s love. It sounds cliche, but it was not when it came from my own experience.</p><p><strong>Insights</strong></p><p>Vipassana means insight, the tradition of this practice emphasizes insights (wisdom) gained from one’s own experience.</p><p>I have gained lots of insights from my Vipassana practice. Some of them are pretty difficult to acknowledge because these insights (awareness) damage the delicately maintained image of myself in front of myself. Another way to put it: my ego didn’t like these insights.</p><p><strong>Awareness &amp; the ability to be present</strong></p><p>It’s hard not to talk about awareness and the ability to be present when you talk about meditation these days. And yes, my ability to be aware and present significantly and visibly improved. These improvements, along with being able to stay positive, loving and kind, made things that were previously impossible for me possible: thinking about difficult conversations at work or with family members.</p><p><strong>Practice</strong></p><p>Many meditators say that it’s challenging to maintain the practice after a 10-day course.</p><p>It <em>is</em> pretty difficult if the intent is “to keep the practice”. It’s like going to the gym just to keep the exercise going, instead of having a more rewarding goal: getting relaxed, meeting friends, having a good time with oneself in the evening or in the morning.</p><p>When I took my first 10-day course, I was dealing with pretty toxic situations at work. After taking the course, I found myself drawn to the practice. I sat one hour in the morning before going to work, and this helped me go through the day knowing that my decisions and communications came from a grounded state of being. After dinner, I sat for another hour, and I could sleep very well. When I missed a sit, I could tell there was something off during the day, and I would get back to my daily sits. It wasn’t me having a big drive for “keeping” the practice, the practice was a necessity.</p><p>Right now, I sit for one hour in the morning, and I know this is how I can get through the day highly productive and positive (sometimes being authentically positive is the only way to being productive).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecfe9795967e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pulse, Stats APIs from Envoy Mobile]]></title>
            <link>https://eng.lyft.com/pulse-stats-apis-from-envoy-mobile-6db71c6a2f22?source=rss-12d33c76c331------2</link>
            <guid isPermaLink="false">https://medium.com/p/6db71c6a2f22</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[mobile-development]]></category>
            <category><![CDATA[stats]]></category>
            <category><![CDATA[logging]]></category>
            <category><![CDATA[envoy-proxy]]></category>
            <dc:creator><![CDATA[Jingwei Hao]]></dc:creator>
            <pubDate>Thu, 17 Dec 2020 18:11:43 GMT</pubDate>
            <atom:updated>2020-12-19T00:42:25.340Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introducing Pulse: Envoy Mobile’s stats library</h3><p>Early this year, we published a <a href="https://eng.lyft.com/envoy-mobile-v0-2-deep-dive-7ed262cfdf93">deep dive</a> after the v0.2 release of Envoy Mobile. A lot has happened since then: Envoy Mobile is now enabled in the production Lyft apps and the open source project recently <a href="https://eng.lyft.com/envoy-mobile-joins-the-cncf-99aee4bdb32e">joined the CNCF</a>. Today, we are excited to announce Pulse, Envoy Mobile’s stats solution.</p><h3>Stats APIs for mobile? Why?</h3><p>In February, we published a blog post detailing <a href="https://eng.lyft.com/observability-for-the-missing-hop-6688c6f3911a">how Envoy Mobile enabled a new range of end-to-end observability of our network</a>. Pulse is a continuation of this work.</p><p>Real-time observability is essential for server-side development. There are existing industry standard open source solutions, such as Prometheus and StatsD. Service owners are accustomed to instrumenting and monitoring their services with various metric types like counters, gauges, and histograms. In comparison, on mobile, observability has conventionally focused on crash reporting and event tracking:</p><p><strong>Crash reporting</strong>: Apps typically use third party reporting tools focused on crashes and exceptions, such as Crashlytics or Bugsnag.</p><ul><li>Pros: These tools usually report events with relatively low latency (usually minutes-level).</li><li>Cons: The reporting is only focused on crashes and exceptions. Additionally, these tools are usually not configurable or extensible. For instance, it’s difficult to integrate them with alarm systems like PagerDuty.</li></ul><p><strong>Event tracking</strong>: Many apps use in-house or third party systems to gather analytics events like user interactions, diagnostic data, etc. for different purposes.</p><ul><li>Pros: compared with the crash reporting systems, the analytics events systems usually allow for custom structured data. This affords performing ad-hoc queries to gather insights about specific features of the apps.</li><li>Cons: data usage is relatively high (compared with crash reporting). Therefore, data reporting resolution is usually in the longer-than-minutes range.</li></ul><p>In order to reduce the time for anomaly detection and to save developers’ time on triaging issues in different areas, <strong>Pulse provides a set of easy to use APIs for mobile engineers to report time-series data (think data points) from their apps</strong>. These time-series then get populated into observability systems and are used to render real-time stats.</p><p>At Lyft, we recently started integrating real-time stats into our clients. Using these stats, we were able to build a dashboard that tracks app crashes and enable a corresponding set of PagerDuty alerts. Previously, engineers relied solely on the Bugsnag UI and fished for crashes for specific releases. It was manual and time consuming. Time to root cause issues was delayed by our inability to know immediately when our apps were not behaving as expected. Now, when the app crash metric spikes, our mobile on-call engineers get paged and immediately start acting on the incident.</p><p>A few weeks ago, the app crash metric spiked for Lyft’s rider app. Thanks to an alert driven by these stats, the on-call engineers were paged immediately. The engineers were able to act on the issue quickly and merged a hot-fix for the incident, and were able to minimize the potential impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1lzFcERUn8gvF2VUW99p3A.png" /><figcaption>app_crash count metric spiked at ~9:55am PT on Nov. 9</figcaption></figure><p>Another valuable aspect of real-time stats is monitoring specific areas of the Lyft apps. Pulse’s stats APIs are flexible and can be applied to any area of the codebase. For example, if the count of taps on the “Request a Ride” button (a relevant interaction for the Lyft rider app) suddenly spikes or drops, it likely suggests a problem worth investigating.</p><h3>What are the APIs and how does Pulse work?</h3><p>Currently, Pulse supports two types of stats: Counter and Gauge.</p><p><strong>Counter:</strong> a value that can be incremented.</p><p>Many mobile apps use analytics for tracking occurrences of an event. Conceptually, this practice acts as a counter. Taking the example from the previous section, traditionally when a user tapped the “Request a Ride” button, an analytic event was emitted. With Pulse, the app instead has a “request_ride” counter that is incremented every time when the user taps the button.</p><p><strong>Gauge: </strong>a value that can be incremented or decremented.</p><p>Gauge stats are less common in mobile development compared to Counters. A simple example is a gauge to report the amount of network connections in flight for an app at a given time. The amount of network connections in flight is a useful metric to observe in real-time: when there is an anomaly (a sudden spike or a drop) for this metric, it most likely means there is something wrong.</p><p>There is a third type of stats we plan to support, it’s Histogram.</p><p><strong>Histogram:</strong> a histogram samples observations and counts them in configurable buckets.</p><p>For example, reporting request durations or time-to-interact on fresh app starts.</p><p>If you want to read more about Pulse’s APIs and how to use them, check the <a href="https://envoy-mobile.github.io/docs/envoy-mobile/latest/api/stats.html">documentation</a>, along with some <a href="https://github.com/envoyproxy/envoy-mobile/tree/main/examples">example apps</a> for both iOS and Android.</p><h4>Reporting stats to the server</h4><p>Client stats are received server-side by a <a href="https://github.com/envoyproxy/data-plane-api/blob/8987b3c53f363676843084c2b75eab4bee2a92e9/envoy/service/metrics/v2/metrics_service.proto#L22">gRPC service</a> based on <a href="https://github.com/statsd/statsd">StatsD</a>. The service expects <a href="https://github.com/envoyproxy/go-control-plane/blob/5d7dab350af2fdbfab6603de2e4b2fd6f82b5ebd/envoy/service/metrics/v2/metrics_service.pb.go#L241">a list of time-series stats</a> serialized as a standard Prometheus <a href="https://github.com/prometheus/client_model/blob/60555c9708c786597e6b07bf846d0dc5c2a46f54/metrics.proto#L87-L91">MetricFamily</a>. The service then flushes the stats to Lyft’s internal observability systems, where they’re used to populate dashboards and alarms. More details on the full end-to-end system are described in a previous observability <a href="https://eng.lyft.com/observability-for-the-missing-hop-6688c6f3911a">blog post</a>.</p><h3>Current status and next steps</h3><p>We are currently working on adding support for Histogram stats to Pulse’s APIs, and are also adding the ability to tag specific stats. With tagging, developers will be able to enrich their stats with different dimensions of information (for example, by adding app_foreground or app_background tags to the app_crash stats mentioned above, providing more insight into the conditions during which the app crashes happen).</p><p><strong>Our goal is to make time-series metrics not only a tool for mobile development, but a necessity: it should become second nature for development teams to consider what stats they want to monitor on their mobile clients to track performance.</strong> We’ve already begun piloting Pulse at Lyft with other feature teams, and are excited to share more of our discoveries as we make progress on Pulse.</p><p>In the meantime, feel free to <a href="https://github.com/envoyproxy/envoy-mobile/tree/main/examples">try it out</a>, <a href="https://github.com/lyft/envoy-mobile/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22">contribute</a>, or review our <a href="https://github.com/lyft/envoy-mobile/milestones">roadmap</a>!</p><h3>Acknowledgements</h3><p>We would like to thank the following teammates for their work and contributions:</p><p>Michael Schore, Jose Nino, Alan Chiu, Michael Rebello, Rafal Augustyniak, Don Yu, and Miguel Juarez</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6db71c6a2f22" width="1" height="1" alt=""><hr><p><a href="https://eng.lyft.com/pulse-stats-apis-from-envoy-mobile-6db71c6a2f22">Pulse, Stats APIs from Envoy Mobile</a> was originally published in <a href="https://eng.lyft.com">Lyft Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>