<?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 Christine Quan on Medium]]></title>
        <description><![CDATA[Stories by Christine Quan on Medium]]></description>
        <link>https://medium.com/@cquantified?source=rss-1611ac0fa58e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GOuo4z-d5eZsyrj937AKSA.png</url>
            <title>Stories by Christine Quan on Medium</title>
            <link>https://medium.com/@cquantified?source=rss-1611ac0fa58e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:55:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cquantified/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[From data informed to data deluded: the hidden costs of tracking too many metrics]]></title>
            <link>https://medium.com/@cquantified/from-data-informed-to-data-deluded-the-hidden-costs-of-tracking-too-many-metrics-13767ac623a5?source=rss-1611ac0fa58e------2</link>
            <guid isPermaLink="false">https://medium.com/p/13767ac623a5</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Christine Quan]]></dc:creator>
            <pubDate>Sun, 19 Mar 2023 21:04:43 GMT</pubDate>
            <atom:updated>2023-03-19T21:04:43.329Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G3eNpcdMrDvh_-eDiKD3nA.jpeg" /></figure><p>As a data scientist who has worked on many metrics and reporting projects throughout my data career, I am one of the first people who will advocate for leveraging data to make business decisions. When used properly, data is beneficial is helping us become more efficient decision makers- which in turn can lead to better business outcomes.</p><p>However, in this post, I offer a warning: more metrics does not mean better decisions. Tracking a useful metric is costly and consuming too many metrics is often more distracting than helpful.</p><h3>The Purpose of a Metric</h3><p>It’s easy to get swept up in the process of creating metrics and reporting processes and forget what the purpose of a metric is. A metric is meant to measure impact — it is not the impact to the product or business itself. Metrics are like the fancy thermometers and tools you would use to cook a turkey — but without an actual turkey in the oven, the dozens of thermometers that you have is essentially meaningless.</p><h3>The Cost of Creating and Monitoring a Metric</h3><p>In today’s world, there is an illusion that data is abundant and bountiful and it is easy to track anything on a whim. This is probably because the many Business Intelligence tools make it very simple to create a chart and put it on a dashboard. While it is easy to create a series of numbers to display on a dashboard, it actually takes a lot of time and thought to create a metric that is actually useful and will help with decision making.</p><p>In today’s world, it is easy to fall into the trap of creating metrics for the sake of having metrics. But if metrics are poorly designed from the beginning, this will end up being costing the business operational resources.</p><h4>Why good metrics are expensive to create and maintain:</h4><ul><li>A good metric takes time and expertise to design. If you don’t put care and thought into designing your metric, it can lead to incentivizing incorrect behaviors. The canonical example of this is the story of the cobra effect — where in the 1800s the British government put a placed a bounty on dead cobras. The intent was to reduce the number of cobras and thereby reduce the risk of people being bitten a cobra. What actually happened was that people started breeding cobras instead — which probably exacerbated the original problem.</li><li>A good metric is dependent on having reliable and clean data pipelines in order to support it. Without this, your metric runs the risk of being incorrect or absent when you need it most.</li><li>A good metric has a maintenance cost. Whether it is upkeep of a data pipeline or having a dedicated individual or team be able to explain a metric and diagnose why a metric is showing a specific trend, a good metric requires a data expert to spend time and investigate trends when they show up in a metric.</li></ul><h3>Managing your Metric Information Diet</h3><p>Those that seek to use data to aid their decision often mistake the security of having many metrics at your finger tips as being data-informed. While tracking hundreds of metrics across dozens or hundreds of dashboards can give the illusion of being data-informed, more often than not, it can distract from solving real problems or innovating. We all have limited time and attention to spend and spreading our focus across too many metrics can distract from solving real business and product problems.</p><p>In statistics, there is a principle called the multiple comparison problem. The issue is most relevant when you are running an experiment and choose to monitor outcome variables. The idea is that the more variables you measure and metric, the higher chance you will have of creating false positive signals and having one metric that moves in a direction that you want.</p><p>A good metric makes sense to monitor on the cadence that you require. Daily, weekly, monthly, quarterly, annual — these are all different cadences that you can monitor a metric. But monitoring metrics too frequently will more often result in attention spam. It’s similar to news: check in on the news every day and there will be something to satisfy your curiosity but is it really meaningful news or just noise? If you instead just check a weekly new report like the Economist, most of the hourly or daily noise will be filtered with the perspective of time. It’s recommended that you try to mirroring your consumption of metrics with how often there is a meaningful trend change that occurs with the metric.</p><h3>Recommendation</h3><ul><li>Limit your portfolio of metrics consumption to only the most high impact data points. Try not to include too many redundant, similar, or duplicative metrics or reporting flows.</li><li>Treat building out a new metric as a long term investment and spend time to do it correctly and thoughtfully. Taking short cuts will lead to bad data points that will cause poorly informed decisions.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13767ac623a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art of the WBR: What I learned about weekly business reviews and data reporting by reading…]]></title>
            <link>https://medium.com/@cquantified/the-art-of-the-wbr-what-i-learned-about-weekly-business-reviews-and-data-reporting-by-reading-da35e976b537?source=rss-1611ac0fa58e------2</link>
            <guid isPermaLink="false">https://medium.com/p/da35e976b537</guid>
            <category><![CDATA[business-intelligence]]></category>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[data-reporting]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[business-reporting]]></category>
            <dc:creator><![CDATA[Christine Quan]]></dc:creator>
            <pubDate>Tue, 25 Jan 2022 06:28:17 GMT</pubDate>
            <atom:updated>2022-01-26T00:32:10.674Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Art of the WBR: What I learned about weekly business reviews and data reporting by reading “<em>Working Backwards”</em></h3><blockquote>This post is a list of interesting takeaways about reporting and leveraging data in business processes that I got while reading Chapter 6 (Metrics) of Colin Bryer’s and Bill Carr’s <em>Working Backwards </em>book<em>.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yuV9d5V6sI9Tofzr" /></figure><p>Full disclosure — I did not read the entire book. Being a data practitioner, there was really just one chapter in <a href="https://www.amazon.com/Working-Backwards-Insights-Stories-Secrets/dp/1250267595"><em>Working Backwards</em></a><em> </em>that stood out to me above the rest in terms of relevancy. While other chapters discussed things like the <a href="https://writingcooperative.com/the-anatomy-of-an-amazon-6-pager-fc79f31a41c9">Amazon 6 pager</a> or the <a href="https://www.inc.com/justin-bariso/amazon-uses-a-secret-process-for-launching-new-ideas-and-it-can-transform-way-you-work.html">internal press release</a> (while still interesting in their own right), these are all strategies that I had heard of before.</p><p>What <em>was </em>new to me was learning that Amazon seemed to be the originator of the WBR — or Weekly Business Review. Working within the realm of business data for several years, WBRs had always seemed like a fixture in the business world and was something that I had assumed had been around since the beginnings of data. But reading Chapter 6 (Metrics) of <em>Working Backwards </em>made me feel like I reading the origin story of the process that has been such an ingrained element of my life in data analytics and reporting.</p><h3>So what did I learn?</h3><ul><li>How Amazon uses data is largely based on a process that goes by the acronym of DMAIC (Define, Identify, Measure, Analyze, Improve, Control)</li><li>Where many teams and companies get ahead of themselves is trying to skip to improving a metric before correctly define, identifying, measuring, or analyzing the <em>correct </em>metrics.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*qRAjiAnQWAigXCG0YxvCRg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xBFws5QvtlQ1CeiP" /><figcaption>Left — Amazon flywheel (<em>Source: Working Backwards</em>). Right — example Reforge Growth Loop (Source: reforge)</figcaption></figure><h4>Breaking down DMAIC:</h4><ul><li><strong>Define</strong>: The purpose of this step is make sure you are defining the big picture aspects of what makes your business function. The book notes how the purpose of any metrics chosen for frequent monitoring in the WBR should be done to better understand the various components of the Amazon flywheel (pictured above). Being a <a href="https://www.reforge.com/blog/growth-loops">reforge</a> alum, I mostly see the flywheel as Amazon’s <a href="https://www.reforge.com/blog/growth-loops">growth loop</a> or sustainable growth engine.</li><li><strong>Identify</strong>: When we have the big picture of how the business’s growth loop operates, only then can we start to identify what metrics matter. In Amazon’s case, these will be levers that Amazon can directly change (with key word being directly) to influence the Selection, Price, Traffic, Customer Experience components of the Flywheel. Much of the Identify section discusses the importance of input metrics (metrics a business can directly change and control — in Amazon’s case, these are things like price, inventory, number of listings, etc) versus output metrics (metrics like revenue or stock prices that a business cannot directly influence and are downstream of input metrics). While output metrics are undeniably important, they are not as actionable as input metrics since a company does not have direct influence over them.</li><li><strong>Measure: </strong>This section gets down to the business of actually collecting and measuring a metric. <br>- Often in the digital age, people think data is just readily available. But when you work in data long enough, you know that sometimes lots of new tools and processes and infrastructure needs to be built before you can a accurately collect the data you need. <br>- Here the authors also note the importance of having the Finance team be an independent body that does not get emotionally invested in the uptick or downtick of a metric and can just objectively call a trend in a metric. <br>- Another interesting note here is when the authors brought up how tracking the wrong metrics can cause misleading or undesirable solutions. One example they gave is around how number of listings was an original WBR metric that had to refined over time in order to get it to a place where it was inspiring the right actions and solutions from the teams in the company. At face value, number of listings was important since it helped them measure the Selection component of the flywheel. But when teams initially fixated too much on improving this metric, they would produce a lot of listing pages for products that the customers did not seem interested in or for products that Amazon did not actively have ready to ship.<br>- The most interesting takeaway here for me is that because WBR metrics can be leveraged so much in business decisions, there should be regular iterations, updates, edits, and audits of these metrics to make sure they are actually relevant to the current state of the business. As data collection can sometimes have hidden bias, qualitative audits (compare with customer anecdotes) are also helpful as a strategy to help make sure the metrics are measuring what a business thinks it is measuring.</li><li><strong>Analyze: </strong>This step is most familiar to anyone who has ever been responsible for explaining trend deviations in a WBR. The goal of this step is to be able why a metric might move beyond normal variation. One method for tackling this is to ask “why” five times until a root cause is identified. One possible output of the investigations is the exception report that details the “whys” or root causes while providing a corresponding action or next step for how to fix or improve each “why” so that it does not cause the same undesirable trend in the future.</li><li><strong>Improve: </strong>Only after having good, actionable metrics in place for monitoring can a business begin to work towards making meaningful improvements as this is when a business is measuring actual signal as opposed to extraneous metrics that they either cannot control or does not have much relevant bearing on the business. Otherwise, any “improvements” will likely result in metrics changes that don’t amount to material changes for the business.</li><li><strong>Control: </strong>The most interesting takeaway from the Control step is understanding that WBRs should evolve and adapt over time to the needs of the business. Another important note is to frequently do WBR process audits and understand when to automate things (automation happens after iterating several times on metrics and having that metric withstand the test of time and usefulness). Once that happens, new processes and tools can be created to support that metric.</li></ul><h3>The WBR document and meeting</h3><ul><li>The actual WBR document should be an “end to end narrative” of the business that follows the customer journey throughout their interaction with the product.</li><li>The WBR document will contain many charts. Baselines and trendlines are critical for contextualizing trends. Some examples of this include YoY growth rates and prior year values. Customer anecdotes can also help add context to the data as well.</li><li>Within the document, standardize chart formats to make it easier to read, interpret, and scan for exceptions (major deviations from normal variation). You don’t want people to have to waste time trying to figure out how to read 10 different styles of charts.</li><li>For the tone of the meeting, set high standards so that people take ownership and pride in the metrics but also make it a safe space for people to openly discuss why metrics might not be trending in a desirable direction. Reward and praise these desirable behaviors of transparency so that it is reinforced over time.</li></ul><p>Overall, the chapter took me under an hour to finish reading and mulling over. Although I have been compiling WBRs and done data reporting for many years, this chapter really helped me take a step back and consider how the processes I currently work with can be better honed and improved. I especially appreciated the reminder just because a business is tracking a list of metrics does not inherently make it truly data driven. It is much more important to make sure that the business is tracking the <em>right</em> metrics that can illuminate real signal and insight to a business’s specific growth loop. And of course, the set of metrics important to business should be iterated on and allowed to evolve over time to ensure that it remains relevant to the business’s current needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da35e976b537" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Twitter Emoji Analysis: An Airbnb Story]]></title>
            <link>https://medium.com/data-science/the-data-files-twitter-emoji-analysis-987093f9c1ee?source=rss-1611ac0fa58e------2</link>
            <guid isPermaLink="false">https://medium.com/p/987093f9c1ee</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[emoji]]></category>
            <dc:creator><![CDATA[Christine Quan]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 19:28:52 GMT</pubDate>
            <atom:updated>2017-12-07T22:20:11.481Z</atom:updated>
            <content:encoded><![CDATA[<p>Emojis and data are two of my favorite things and I have been itching to combine them in a fun project. A few weeks ago, as I was scrolling through my twitter feed, inspiration struck:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*t3edsoG7_tK6574hlx1bFQ.png" /><figcaption>Describe your dream trip in three emojis.</figcaption></figure><p>See the project <a href="https://christinequan.github.io/airtweets/">here</a>.</p><h3>The Process</h3><h4>1. Scrape the data:</h4><p>At first I thought scraping would be simple since all I needed to do was query the twitter API. <em>Surely</em>, there was an endpoint that would give me the responses to a specific tweet. But alas, this was not the case. After several hours of googling and stack-overflowing, I found some possible solutions. But what I ended doing was using the following rscript (with help from @HamdanAzhar from @PRISMOJI)</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e9858a73a86357ab1cf5690480087c0b/href">https://medium.com/media/e9858a73a86357ab1cf5690480087c0b/href</a></iframe><p>The workaround is essentially get all mentions of the original account. And then filter those mentions with the original tweet id. It’s better to do this as soon as possible since for popular accounts, you might need to gather hundreds of thousands of responses before you get the full set. Another caveat is the free API account currently only allows queries as far back as 7 days. So make sure to collect responses within the week.</p><h4>2. Translating emojis into English:</h4><p>Once I had the data, I had to convert the unicode into english so I could better filter and analyze the data. While there are a few unicode &lt;&gt; english dictionaries out there, I happen to be working in R and on a windows machine (so I had some pretty obscure encodings to work with). After several hours of frustration, I finally arrived at a solution that worked. I first extracted the emojis from the comments since some of them also had extraneous text. From there, I did a few stringr manipulations to get the format I needed and used this dictionary to translate my emojis.</p><h4>2. Analyze and clean the data:</h4><p>After I was done translating the emojis, I was finally ready for analysis. I primarily used the tidytext library to work with the dataset.</p><p>I also wanted to categorize the different emojis. After thinking of writing a classifier (hi scipy) or using <a href="https://wordnet.princeton.edu/">Princeton’s Wordnet</a>, I ultimately decidedly against both. Neither solutions offered exactly what I wanted and since my dataset had just about 150 unique emojis(small by dataset standards), I decided to just bite the bullet, pop on my favorite Spotify playlist, and hand-code the categories that I wanted.</p><h4>3. Visualize the Data</h4><p>One of primary goals from the beginning was to build a custom d3 chord to visualize the different pairings of emojis. Since this was my first time building this sort of d3 chart, I had a bit of learning to do. In particular, there was the radial scale for positioning, how to append custom images(the emojis)to an svg, and how to create perfect arcs.</p><p>After figuring all of that out, I arrive at this (tada!): Click <a href="https://christinequan.github.io/airtweets/">here</a> for the interactive version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*_XqDbS3wecPAV99IJsE1-g.png" /><figcaption>Airbnb Twitter Emoji Chord. See interactive version here: <a href="https://christinequan.github.io/airtweets/">https://christinequan.github.io/airtweets/</a></figcaption></figure><p><strong><em>Thanks for reading! Let me know if you have any feedback or questions about how I made this. Follow me to read more about data visualization, mini tutorials, and various data projects I am working on. :)</em></strong></p><p><strong><em>Christine</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=987093f9c1ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-science/the-data-files-twitter-emoji-analysis-987093f9c1ee">Twitter Emoji Analysis: An Airbnb Story</a> was originally published in <a href="https://medium.com/data-science">TDS Archive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Data Files: Twitter Emoji Analysis]]></title>
            <link>https://code.likeagirl.io/the-data-files-twitter-emoji-analysis-7703ea2a6238?source=rss-1611ac0fa58e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7703ea2a6238</guid>
            <category><![CDATA[emoji]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[codelikeagirl]]></category>
            <dc:creator><![CDATA[Christine Quan]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 02:52:01 GMT</pubDate>
            <atom:updated>2017-12-07T00:20:34.442Z</atom:updated>
            <content:encoded><![CDATA[<p>Emojis and data are two of my favorite things and I have been itching to combine them in a fun project. A few weeks ago, as I was scrolling through my Twitter feed, inspiration struck:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*t3edsoG7_tK6574hlx1bFQ.png" /><figcaption>Describe your dream trip in three emojis.</figcaption></figure><p>See the project <a href="https://christinequan.github.io/airtweets/">here</a>.</p><h3>The Process</h3><h4>1. Scrape the data:</h4><p>At first I thought scraping would be simple since all I needed to do was query the twitter API. <em>Surely</em>, there was an endpoint that would give me the responses to a specific tweet. But alas, this was not the case. After several hours of googling and stack-overflowing, I found some possible solutions. But what I ended doing was using the following rscript (with help from @HamdanAzhar from @PRISMOJI)</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e9858a73a86357ab1cf5690480087c0b/href">https://medium.com/media/e9858a73a86357ab1cf5690480087c0b/href</a></iframe><p>The workaround is essentially get all mentions of the original account. And then filter those mentions with the original tweet id. It’s better to do this as soon as possible since for popular accounts, you might need to gather hundreds of thousands of responses before you get the full set. Another caveat is the free API account currently only allows queries as far back as 7 days. So make sure to collect responses within the week.</p><h4>2. Translating emojis into English:</h4><p>Once I had the data, I had to convert the unicode into english so I could better filter and analyze the data. While there are a few unicode &lt;&gt; english dictionaries out there, I happen to be working in R and on a windows machine (so I had some pretty obscure encodings to work with). After several hours of frustration, I finally arrived at a solution that worked. I first extracted the emojis from the comments since some of them also had extraneous text. From there, I did a few stringr manipulations to get the format I needed and used this dictionary to translate my emojis.</p><h4><strong>2. Analyze and clean the data:</strong></h4><p>After I was done translating the emojis, I was finally ready for analysis. I primarily used the tidytext library to work with the dataset.</p><p>I also wanted to categorize the different emojis. After thinking of writing a classifier (hi scipy) or using <a href="https://wordnet.princeton.edu/">Princeton’s Wordnet</a>, I ultimately decided against both. Neither solutions offered exactly what I wanted and since my dataset had just about 150 unique emojis (small by dataset standards), I decided to just bite the bullet, pop on my favorite Spotify playlist, and hand-code the categories that I wanted.</p><h4>3. Visualize the Data</h4><p>One of primary goals from the beginning was to build a custom d3 chord to visualize the different pairings of emojis. Since this was my first time building this sort of d3 chart, I had a bit of learning to do. In particular, there was the radial scale for positioning, how to append custom images(the emojis)to an svg, and how to create perfect arcs.</p><p>After figuring all of that out, I arrive at this (tada!): Click <a href="https://christinequan.github.io/airtweets/">here</a> for the interactive version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*_XqDbS3wecPAV99IJsE1-g.png" /><figcaption>Airbnb Twitter Emoji Chord. See interactive version here: <a href="https://christinequan.github.io/airtweets/">https://christinequan.github.io/airtweets/</a></figcaption></figure><p><strong><em>Thanks for reading! Let me know if you have any feedback or questions about how I made this. Follow me to read more about data visualization, mini tutorials, and various data projects I am working on. :)</em></strong></p><p><strong><em>Christine</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7703ea2a6238" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/the-data-files-twitter-emoji-analysis-7703ea2a6238">The Data Files: Twitter Emoji Analysis</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I used social media to jump start my journey in learning data visualization engineering]]></title>
            <link>https://code.likeagirl.io/how-i-used-social-media-to-jump-start-my-journey-in-learning-data-visualization-engineering-d3f1657876fd?source=rss-1611ac0fa58e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3f1657876fd</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[codelikeagirl]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Christine Quan]]></dc:creator>
            <pubDate>Thu, 02 Nov 2017 02:08:30 GMT</pubDate>
            <atom:updated>2017-11-02T14:09:00.926Z</atom:updated>
            <content:encoded><![CDATA[<p><em>TLDR: This is a post reflecting on how I started learning web-based data visualization. Read this if you’re interested in getting started with learning how to build web-based visualizations or want to read ideas on how to use social media when learning anything to manage your information consumption.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0FzUZyKI6evBus38mKyGTQ.jpeg" /></figure><p>When starting out with any new field, I try to absorb as much information about the field as possible. This helps me understand the fundamentals as well as where the field currently is. Using social media is a great way to tailor my information diet to just what I need. While social media can be a huge time sink, its customization capabilities make it an incredible tool for learning when used deliberately.</p><ol><li><strong>Twitter</strong>: I use twitter to follow people and organizations. The great thing about twitter is that I can tailor it to fit my information consumption needs (currently, that is anything and everything web dev and data viz). You can also create lists to further help your organize your twitter feed. Here are two of my lists: <a href="https://twitter.com/quizzicalquan/lists/code">Code</a> and <a href="https://twitter.com/quizzicalquan/lists/data-viz">Data Viz</a>. <em>Check them out for ideas of who to follow or simply follow the lists so you don’t have to reinvent the wheel :)</em></li><li><strong>Youtube</strong>: Similar to Twitter, I create playlists of Ted or tech talks that I find interesting. Then I can play these whenever I have a free 30 minutes to spare or when I need to break from coding. <em>Aside: I also use playlists to organize workouts so I have them ready to go. It really helps balance the explore/exploit ratio in my web surfing.</em></li><li><strong>Medium: </strong><a href="https://medium.com/towards-data-science">Towards Data Science</a>, <a href="https://medium.freecodecamp.org/">freeCodeCamp</a>, <a href="https://hackernoon.com/">Hacker Noon</a>, and <a href="https://code.likeagirl.io/">Code Like a Girl</a> are all great publications that provide great articles and coder communities.</li><li><strong>Quora: </strong>I tend to use Quora for bigger picture questions: like what is the state of data visualization or data science or how to prepare for interviews. I don’t tend to use it for technical questions but it’s a great way to learn about the experiences of others.</li><li><strong>reddit: </strong>I am not an avid redditer but I do occasionally drop in on the following subreddits: <a href="https://www.reddit.com/r/dataisbeautiful/">Data is Beautiful</a> and <a href="https://www.reddit.com/r/reactjs/">ReactJS</a>.</li><li><strong>Facebook</strong>: Two active pages I follow is <a href="https://www.facebook.com/rbloggers/">RBloggers</a> and <a href="https://www.facebook.com/rstudioinc/posts/1573390802685354">Rstudio</a>. I have tried following JS and other web dev pages but I think these communities are more active on twitter than Facebook.</li><li><strong>Pinterest</strong>: I have had a Pinterest account for a long time and have the expected fashion, baking, and crafts boards. But recently, I have also started using it for <a href="https://www.pinterest.com/cquantified/data-visualization/">data visualization inspiration</a> as well. <a href="https://www.pinterest.com/nadiehbremer/">Nadieh Bremer</a> is my favorite Pinterest profile to follow for data visualization as well.</li><li><strong>Github</strong>: Many authors in Medium articles or blogs will often link to code in their github profiles. In addition to individual profiles, I have found it extremely helpful to also read code repositories for open-source projects to learn new styles, patterns, and techniques.</li><li><strong>StackOverflow: </strong>This is a given. But I will include it for completeness. Most likely, the first time you run into a technical question and type it into google, you will have seen this site.</li><li><strong>Email Lists and Blogs: </strong>There are so many individual blogs and email lists that have amazing content. Currently, two that I like are Swizec Teller’s <a href="https://swizec.com/blog/">blog</a> (for front-end) or Val Head’s <a href="http://uianimationnewsletter.com/">weekly animation newsletter</a>.</li></ol><p><em>I hope this gives you ideas on ways to tailor your information diet for your learning needs. Let me know in the comments below if there are other ways you use social media to learn or other data visualization social media resources I am missing!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3f1657876fd" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/how-i-used-social-media-to-jump-start-my-journey-in-learning-data-visualization-engineering-d3f1657876fd">How I used social media to jump start my journey in learning data visualization engineering</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You are enough — what I learned from a summer of breathe. code. love.]]></title>
            <link>https://code.likeagirl.io/you-are-enough-what-i-learned-from-a-summer-of-breathe-code-love-7b43ab3bba5e?source=rss-1611ac0fa58e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b43ab3bba5e</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[codelikeagirl]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Christine Quan]]></dc:creator>
            <pubDate>Wed, 01 Nov 2017 23:56:42 GMT</pubDate>
            <atom:updated>2017-11-02T14:18:13.238Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tK650kwYOwaMnyPlSvBNXQ.jpeg" /></figure><p>This past summer, I committed myself to becoming a better engineer. I also decided to seriously invest in my mental, emotional and physical well-being.</p><p>That led me to spend my days either reading about my programming, practicing yoga, coding, or simply spending time with family and friends.</p><p>In my quest to start my yoga routine, I stumbled upon Juliana’s <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=1&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwii8aWYkIPXAhXixFQKHSkQDsUQFggmMAA&amp;url=https%3A%2F%2Fwww.youtube.com%2Fuser%2Fcexercize&amp;usg=AOvVaw3pMYfkTQgG3a9JlAUdhu85">Boho Beautiful</a> channel. It was perfect — most of the videos ranged from 10–30 minutes, perfect to insert into a busy day. I was merely trying to increase my fitness routine but surprisingly found that by the end of the month, I was in the best shape I had every been. I wasn’t in any particular rush to reach any sort of fitness goal but in between guiding me through warrior poses and telling me to take ever-deeper breaths, Juliana kept reminding me that wherever I was in my practice, it was ok. I just needed to be patient with myself and my body and the mastery will come. I was exactly where I needed to be.</p><p>Those words came back to me one day as I was scrolling through the dozens of YouTube videos and coding tutorials I had bookmarked — wondering, when, if ever, I was going to feel competent in coding. And then I started to feel panicked — wondering if I was fighting a lost cause. How was I supposed to catch up and learn everything?!? The list of things I knew I didn’t know was growing so much faster than the list of things I knew how to do. And that difference was causing me anxiety.</p><p>When you’re just starting out as a programmer, it can feel like you’re staring up a huge insurmountable mountain with no idea how to even start scaling it.</p><p>And then you try to Google tutorials and you get results that only seem to expand the list of things you know you don’t know, confirming your deepest fears.</p><p>Suddenly, despair sets in and you start to doubt whether you can really program - whether you are really cut out for any of this.</p><p>But don’t despair, after two months of starting my yoga fitness routine, I started to realize that while it’s good to push yourself and grow, you should try not to let negative, doubtful thoughts cloud that process. You will feel frustrated with yourself when the code is not behaving as it should. You will feel frustrated when you are simply not grasping a new syntax or framework. It’s ok.</p><p>When that happens, I let the emotion run it’s course and then I take a deep breath and remind myself it’s all a journey. I am trying my best. As long as you show up and do your work, the understanding and skill will come. Be patient with yourself. You will get there…the frustration will only slow that process down.</p><p>Just focus on your craft and the skills will come.</p><p>So wherever you are in your coding journey, if you ever find yourself feeling frustrated that something isn’t coming together quick enough, just have patience with yourself. Breathe. You are enough.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b43ab3bba5e" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/you-are-enough-what-i-learned-from-a-summer-of-breathe-code-love-7b43ab3bba5e">You are enough — what I learned from a summer of breathe. code. love.</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>