<?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  on Medium]]></title>
        <description><![CDATA[Stories by  on Medium]]></description>
        <link>https://medium.com/@mythoughtsanddata?source=rss-95e1c707eebb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CRokM1Iteq3GLzkdVpoleQ.jpeg</url>
            <title>Stories by  on Medium</title>
            <link>https://medium.com/@mythoughtsanddata?source=rss-95e1c707eebb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:46:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mythoughtsanddata/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[How Documentation Made My Job Easier]]></title>
            <link>https://code.likeagirl.io/how-documentation-made-my-job-easier-6c58d044d9e3?source=rss-95e1c707eebb------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c58d044d9e3</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-analyst]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <pubDate>Tue, 09 Dec 2025 23:43:16 GMT</pubDate>
            <atom:updated>2025-12-09T23:43:18.595Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wDvWNkJfKz2eeKSM-gsaEQ.png" /><figcaption>AI generated image</figcaption></figure><p>As the year comes to an end, I find myself looking back on some of the habits that quietly made my work easier. Not the big technical milestones or the new tools I learned, but the small shifts that reduced stress, created clarity, and made my work easier for others to understand.</p><p>Documentation is one of those shifts. Not the long, formal documentation that lives in forgotten folders. The simple notes help you remember why you made a decision, explain your logic clearly, and make your work reproducible long after you have moved on to the next task.</p><p>But here is the truth, many analysts discover late:<br>“Documentation does not slow you down. It prevents you from being slowed down”.</p><p>It protects your credibility when someone asks, “How did you get this number?” It eliminates unnecessary back-and-forth questions. And it helps future you, who will not remember half the decisions you made.</p><p>So I wanted to share the practical documentation habits that helped me keep my work clean, clear, and scalable over the years.</p><h4>Document While You Work, Not After</h4><p>Documentation written at the end becomes a story you are trying to reconstruct. While documentation written during the work becomes accurate, honest, and useful.</p><p>The easiest way to start is to keep a running note open in Notion, OneNote, or even a plain-text file (my go-to). Capture the things you would normally forget:</p><ul><li>Why did you choose a filter</li><li>What business rule changed</li><li>A small assumption you made</li><li>Something unusual you noticed in the data</li></ul><p>These tiny decisions are exactly what someone will ask about later.</p><h4>Focus on the Essentials</h4><p>Once you get used to capturing notes in the moment, you can shape them into a simple structure. You do not need paragraphs of documentation. You only need to cover the essentials:</p><p>What problem were you solving<br>Example: “Build AHT metric using call-level timestamps.”</p><p>Where the data came from<br>Specific tables, fields, systems, or endpoints.</p><p>The logic you applied<br>Joins, filters, calculations, and assumptions.</p><p>Known limitations<br>Gaps in the data, unusual business processes, or historical inconsistencies.</p><p>Why certain decisions were made<br>The part most people skip, and the part most stakeholders ask about.</p><h4>Store Documentation in the Right Folder</h4><p>If your documentation is buried in a random folder, it does not exist.<br>Keep it close to the work:</p><ul><li>For dbt, write docs in .yml</li><li>For SQL, add comments in your queries, and use Git commit messages</li><li>For Power BI, I create a Notes page inside the report</li><li>For Excel, add a “Logic” sheet.</li></ul><h4>Create Reusable Templates</h4><p>Documentation feels heavy when you have to start from scratch each time. It feels light when you use templates. Here is a simple structure that works for me with almost any task:</p><p>Title:<br>Task:<br>Source Data:<br>Logic Applied:<br>Metrics Defined:<br>Edge Cases:<br>Limitations:<br>Final Output:<br>Where it lives:</p><p>To make this even more practical, I created a public <a href="https://github.com/victoriaao/analytics_documentation_templates/tree/main/templates/analysis">repository</a> with some of the templates I use in my daily work.</p><h4>Why Documentation Matters</h4><p>Documentation is not for compliance. It is for clarity.</p><ul><li>It helps the next person who inherits your model.</li><li>It helps the stakeholder who needs trust in your numbers.</li><li>And it helps your future self, who will not remember why a decision was made.</li></ul><p>Most importantly, documentation turns individual work into shared knowledge. That is how we scale impact and build trust.</p><p>As we wrap up another year, this is a habit worth carrying into the next one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c58d044d9e3" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/how-documentation-made-my-job-easier-6c58d044d9e3">How Documentation Made My Job Easier</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[Analysts Could Use a Little Engineering Thinking]]></title>
            <link>https://code.likeagirl.io/analysts-could-use-a-little-engineering-thinking-07f04a108f61?source=rss-95e1c707eebb------2</link>
            <guid isPermaLink="false">https://medium.com/p/07f04a108f61</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-analysis]]></category>
            <pubDate>Wed, 19 Nov 2025 09:58:02 GMT</pubDate>
            <atom:updated>2025-11-19T09:58:02.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ogw8izBlpIDdPDJhor4bpg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sagefriedman?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sage Friedman</a> on <a href="https://unsplash.com/photos/woman-sitting-on-bench-over-viewing-mountain-HS5CLnQbCOc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Hear me out, I have always loved autonomy at work, the freedom to build, fix, and experiment without waiting on someone else. But being an analyst did not always give me that. I was good at finding answers, writing SQL queries, and building dashboards. Yet whenever something broke upstream, whether it was a failed pipeline refresh, a renamed column, a missing table, or a forgotten join, everything stopped. And if you have worked in analytics long enough, you know that moment well when it is a fix you cannot make.</p><p>That loss of control frustrated me, so I started taking data engineering courses. In the beginning, it felt like a whole new language: pipelines, orchestration, ETL and ELT, dbt models, Git, Airflow, data lineage, warehouses, all of it. I did not fully understand what I was learning, but I stayed with it and kept moving forward.</p><p>Over time, I realized it was not just about new tools. It was about thinking differently. Engineers design for reliability. Analysts often build for right now. But when analysts start thinking like engineers, they stop firefighting and start building foundations that last.</p><h4>Reuse Beats Repetition</h4><p>I used to rebuild the same reports from scratch, new query, same logic, different filters. Many of us have done this without even noticing how much time it quietly consumes.</p><p>Engineers approach problems once, deeply, and then make their solutions reusable. Analysts should do the same. When you modularize logic, standardize joins, or template your transformations, you spend less time fixing and more time interpreting. Good analysis is not about speed. It is about building systems that enable the speedy delivery of insights.</p><h4>Documentation Builds Trust</h4><p>Early in my career, documentation was an afterthought, something I did when someone asked, “How did you calculate this?” And if we are being honest, most analysts learn documentation reactively, not intentionally.</p><p>Then I realized that documentation is more than explanation. It is evidence of thinking. When you document assumptions, business logic, and dependencies, you build transparency. People stop questioning your numbers and start trusting your process. That trust is what gives analysts real influence.</p><h4>Reproducibility</h4><p>A great analysis should be repeatable without your presence. Engineers build pipelines that run daily, cleanly, and consistently. Analysts can do the same by creating reusable models, defining metrics centrally, and parameterizing reports.</p><p>One of the biggest improvements I noticed came when I adopted the <a href="https://learn.microsoft.com/en-us/power-bi/guidance/star-schema"><strong>Star Schema</strong> </a>approach in Power BI. Designing data models with clear dimension and fact tables not only simplified relationships but also significantly improved DAX performance. Queries became faster, calculations were cleaner, and troubleshooting was far easier.</p><p>And if you have ever tried to troubleshoot a slow dashboard or inconsistent metric, you know how quickly poor structure exposes itself. Therefore, when anyone can reproduce your work and get the same result, you have built more than insight. You have built infrastructure.</p><h4>Testing Protects Your Credibility</h4><p>We test dashboards visually far too often and say, “It looks right.”</p><p>Engineers do not guess. They test by adding validation checks, data quality alerts, or dbt tests that catch silent errors before they reach a meeting. Analysts can do the same.</p><p>As an analyst, I often create a dedicated data check page to compare a DAX result against a SQL result or to slice a metric multiple ways to confirm consistent behaviour. If a measure breaks under a simple filter, the model needs work.</p><p>Testing does not slow you down. It protects your reputation even when you are not in the room.</p><h4>Build Once, Scale Everywhere</h4><p>When analysts think like engineers, their work multiplies in value.</p><p>A well-designed model becomes the backbone for multiple dashboards.<br>A single KPI definition becomes the company’s shared language.<br>A documented process becomes a teaching tool for the next analyst.</p><p>I saw this impact firsthand. The documentation and reusable patterns I created eventually led to my being asked to build a full dashboard design system for the company. It showed me that good structure does more than support your work. It elevates it.</p><h4>Where This Leaves Us</h4><p>I know the word “engineering” can sound intimidating, especially if you come from a non-technical or traditional analytics path. But thinking like an engineer is not about becoming one. It is about adopting a mindset that makes your work more reliable, more efficient, and more scalable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07f04a108f61" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/analysts-could-use-a-little-engineering-thinking-07f04a108f61">Analysts Could Use a Little Engineering Thinking</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[Lead How You Wish You Were Led]]></title>
            <link>https://code.likeagirl.io/lead-how-you-wish-you-were-led-b41b51fdf2b6?source=rss-95e1c707eebb------2</link>
            <guid isPermaLink="false">https://medium.com/p/b41b51fdf2b6</guid>
            <category><![CDATA[emotional-intelligence]]></category>
            <category><![CDATA[career-growth]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <pubDate>Thu, 06 Nov 2025 14:34:04 GMT</pubDate>
            <atom:updated>2025-11-06T14:34:04.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9SDnY4RvmpSZzenc3MBmYw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@as_it_is?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Peter Blake</a> on <a href="https://unsplash.com/photos/a-lighthouse-on-a-rocky-outcropping-overlooking-the-ocean-jmmcilwToto?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The first time many of us understand the kind of manager we want to be is not during a promotion. It is in the moments we feel unseen. It is that project where our effort was overlooked. It is that feedback that focused on what went wrong instead of what went right.</p><p>Those moments stay with us, and whether we know it or not, they shape the kind of leaders we become. They teach us that you can hit every target and still miss your people.</p><h4>What It Means to Be the Manager We Needed</h4><p>Being the manager we once needed is not about being soft. It is about being present.</p><p>It looks like:</p><ul><li>Taking five extra minutes to explain why a change matters.</li><li>Saying “thank you” even when the task was expected.</li><li>Giving feedback that builds instead of breaks.</li><li>Checking in when someone seems quieter than usual.</li><li>Remembering that growth is not linear for everyone, and neither is confidence.</li></ul><p>Sometimes, our calmness in chaos teaches more than any instruction ever could.</p><h4>When We See Ourselves in Others</h4><p>Every now and then, we recognize a younger version of ourselves on the team: the overthinker, the quiet one, the eager one, the burnt-out one.</p><p>That is our cue to pause. Not to project our old story onto them, but to guide them through it better than we were guided. That is what growth in leadership looks like: breaking the cycle of what we once lacked.</p><h4>Leading with Empathy, Not Ego</h4><p>Being the manager we needed does not mean lowering standards.<br>It means raising understanding.</p><p>Authentic leadership is not about how well a team performs when everything is smooth. It is about how safe people feel to stumble and still stand beside us.</p><p>The manager we once needed would have said,</p><p><em>“Don’t worry, we will figure it out together.”</em></p><p>Now that is what we say to others. And each time we do, we silently thank our younger selves for noticing what was missing and choosing to become the change.</p><h4>Remember this</h4><p>If you are leading a team today, someone is looking at you the way you once looked at your manager.</p><p>There is a reason the saying goes,<em> “People leave managers, not jobs.”</em></p><p>So, be the reason they stay curious.<br>Be the voice that steadies them when doubt creeps in.<br>Be the manager we all once needed.</p><p>Because leadership is not just about managing others.<br>It is about healing the part of us that once needed better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b41b51fdf2b6" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/lead-how-you-wish-you-were-led-b41b51fdf2b6">Lead How You Wish You Were Led</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[Learning to Be Okay With Not Knowing Everything]]></title>
            <link>https://code.likeagirl.io/learning-to-be-okay-with-not-knowing-everything-4711b01151b5?source=rss-95e1c707eebb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4711b01151b5</guid>
            <category><![CDATA[continuous-learning]]></category>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[professional-growth]]></category>
            <category><![CDATA[editors-pick]]></category>
            <pubDate>Tue, 28 Oct 2025 09:06:01 GMT</pubDate>
            <atom:updated>2025-10-28T23:24:32.595Z</atom:updated>
            <content:encoded><![CDATA[<h4>Embracing the endless learning curve in data analytics</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tHzSa35RgAqpBbxeEFZc7g.jpeg" /></figure><p>When many of us first start working with data, we think success means knowing everything, myself included. It took me a while to realize how wrong I was.</p><p>We want to master every tool: database querying tools like SQL and PostgreSQL, visualization tools like Power BI and Tableau, and scripting languages like Python. We even believe that if we learn enough about APIs and machine learning frameworks, we will finally feel “complete” as data professionals.</p><blockquote>“But here is what no one tells you when you start: the career is a journey, not a destination”</blockquote><p>Every time we learn something new, we uncover ten more things we do not understand. And that realization can be uncomfortable. It can make us feel behind, even when we are not.</p><p>With time, though, we learn to see it differently. Working in data is not about reaching a finish line. It is about learning to be comfortable in the unknown, trusting that curiosity and persistence will carry us further than perfection ever could.</p><h3><strong>The Day I Realised the Finish Line Does not Exist</strong></h3><p>In the early days, many of us felt confident once we could write complex SQL queries, including joins, CTEs (Common Table Expression), window functions, the whole lot. Then came version control, and we were suddenly learning how to create branches, commit changes, and resolve merge conflicts.</p><p>What used to be a simple script now involved pull requests and understanding collaboration rules. It is humbling, but it teaches us something valuable. In data, the learning never stops. When we think we have mastered something, a new layer appears.</p><p>Growth in this field is not linear. It is layered. And every new layer builds humility.</p><h3><strong>Curiosity Over Certainty</strong></h3><p>There was a time when I used to panic if someone asked a question I could not answer. I thought credibility came from always having the right response.</p><blockquote>Now, I simply say, “I am not sure yet, but let us figure it out.”</blockquote><p>That single shift changed everything. It changes how others see us, not as people who know it all, but as people who care about getting it right. In analytics, curiosity is what keeps you relevant. It is what turns data into insight and confusion into progress.</p><h3><strong>Learning in Layers</strong></h3><p>Many of us are learning new tools right now. For me, it is dbt (Data Build Tool).</p><p>When I first opened the interface, I had no idea what models, macros, or Jinja even meant. But instead of trying to master everything at once, I started small, setting up my first model, documenting a source, and committing changes to Git.</p><p>Then I learned more about version control, testing, and eventually, deployment. Each piece made more sense once I had wrestled with the last one. That is how learning in data really works, layer by layer, not all at once.</p><h3><strong>The Imposter Feeling Never Fully Goes Away</strong></h3><p>Even now, when I read articles on data engineering or cloud architecture, there is a quiet voice that says, “You should know this by now.” But with time, you need to learn to answer it with grace:</p><blockquote>“I do not need to know everything. I just need to keep learning.”</blockquote><p>That mindset shift has been liberating. Because in truth, no one in data knows it all. The people we admire most are just the ones who stayed curious long enough to keep growing.</p><h3><strong>Progress Over Perfection</strong></h3><p>The moment I stopped chasing the illusion of “knowing it all,” learning became lighter, more joyful, and far more sustainable.</p><p>I started focusing on what was relevant to my work, not everything that existed or trended online. I stopped trying to learn for the sake of keeping up, and started learning for the sake of growing.</p><blockquote>My mentor once told me, “Even with all my experience, I still Google things every day.”</blockquote><p>That stuck with me.</p><p>Being a great analyst is not about memorizing every function or library. It is about understanding how data moves, connects, and tells stories that drive action.</p><h3><strong>For the Days You Feel Behind</strong></h3><p>If you ever feel overwhelmed by all there is to learn, cloud tools, automation, AI, or whatever is trending next, take a breath.</p><p>You are not behind. You are simply on the same endless learning curve that every good data professional is on. The truth is, you will never know everything. But you can always keep learning.</p><p>And that is more than enough.</p><p>How do you deal with the constant learning curve as a data professional?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4711b01151b5" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/learning-to-be-okay-with-not-knowing-everything-4711b01151b5">Learning to Be Okay With Not Knowing Everything</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[The Soft Skills That Made Me a Better Data Analyst]]></title>
            <link>https://medium.com/@mythoughtsanddata/the-soft-skills-that-made-me-a-better-data-analyst-ca82f0d53646?source=rss-95e1c707eebb------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca82f0d53646</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[soft-skills]]></category>
            <category><![CDATA[workplace-lessons]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[professional-growth]]></category>
            <pubDate>Tue, 16 Sep 2025 20:49:45 GMT</pubDate>
            <atom:updated>2025-09-18T23:54:45.683Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*54oqed6Nr20XOryf-I7NxA.png" /><figcaption>AI-generated digital illustration</figcaption></figure><p>When I started as a data analyst, I thought the job was all about SQL queries, Excel formulas, and dashboards. Don’t get me wrong; those matter. But the longer I’ve been in this role, the more I’ve realized that <strong>soft skills are the real difference-makers.</strong> They’re what help you translate data into impact, and they’re often what separate a good analyst from a great one.</p><p>Here are some of the essential soft skills that shaped my own journey, and why they might matter in yours too.</p><p><strong>Communication: More Than Just Numbers</strong></p><p>Early in my career, I made the mistake of dumping charts and stats into presentations, assuming everyone would “get it.” They didn’t. I had to learn to <strong>tell a story, to explain “the why,” </strong>basically to explain insights in plain language and connect them back to what stakeholders cared about. The best analysis is useless if no one understands it.</p><p><strong>Tip:</strong> Next time you present, try asking yourself: <em>“What’s the one sentence I want them to remember? And what’s the one thing I want them to take away today?”</em></p><p><strong>Curiosity: Asking “Why” Until It Hurts</strong></p><p>The difference between reporting and analysis is curiosity. Anyone can say certain metrics dropped by a percentage e.g., sales dropped 10%. But the analyst who keeps asking <em>“why?”</em> eventually uncovers the real driver. Some of my best breakthroughs came from refusing to settle for the first explanation in the data.</p><p><strong>Critical Thinking: Not Every Correlation Is Gold</strong></p><p>Once, while working on a marketing report, I nearly reported that the marketing spend was driving conversions, only to realize it was <a href="https://metricswatch.com/understanding-the-impact-of-seasonality-on-marketing-metrics"><strong>seasonality</strong></a> at play. That taught me to <strong>question patterns</strong> and stress-test my assumptions. A skeptical mindset isn’t negativity; it’s protecting your credibility.</p><p><strong>Collaboration and Business Acumen</strong></p><p>I used to treat and work on my data as my own little island. But projects really started succeeding when I partnered closely with business teams. Working with the relevant stakeholders, such as product managers, engineers, and even frontline staff, gave me context I couldn’t get from the database. <strong>Collaboration is what turns analysis into action.</strong></p><p>Also, I once spent weeks perfecting a model, only to find out the stakeholders weren’t interested in that metric at all. That experience pushed me to better understand <strong>how the business actually makes decisions.</strong> When you know the levers that matter, your analysis becomes far more impactful.</p><p><strong>Attention to Detail: The Credibility Factor</strong></p><p>Nothing sinks trust faster than sharing numbers that don’t add up. Early mistakes taught me that checking formulas twice and verifying data sources isn’t just diligence; it’s your professional reputation.</p><p><strong>Adaptability: Because Change Is the Only Constant</strong></p><p>There will always be new tools, new data sources, new priorities; it never ends. I’ve had to learn to embrace change instead of resisting it. Adaptability isn’t just about technology; it’s about mindset. It’s saying, “Okay, the rules shifted, let’s figure it out.”</p><p><strong>Wrapping Up</strong></p><p>The technical side will always matter, but the ability to communicate, collaborate, and think critically is what makes the role truly powerful.</p><p>So, if you’re starting out or even years into the field, don’t just invest in your SQL or Python. Invest in your curiosity, your storytelling, and your ability to work with people. Because at the end of the day, data doesn’t speak for itself. <strong>You do.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca82f0d53646" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>