<?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 Tereza Cihelkova on Medium]]></title>
        <description><![CDATA[Stories by Tereza Cihelkova on Medium]]></description>
        <link>https://medium.com/@terezacihelkova?source=rss-7307709952d5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1tDUXU9YTPEdbteVgOX6jw.jpeg</url>
            <title>Stories by Tereza Cihelkova on Medium</title>
            <link>https://medium.com/@terezacihelkova?source=rss-7307709952d5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:39:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@terezacihelkova/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[Analytics as Code — what is it, and how does it help you?]]></title>
            <link>https://medium.com/@terezacihelkova/analytics-as-code-what-is-it-and-how-does-it-help-you-93e9a3c179ee?source=rss-7307709952d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/93e9a3c179ee</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[bi]]></category>
            <category><![CDATA[analytics-as-code]]></category>
            <dc:creator><![CDATA[Tereza Cihelkova]]></dc:creator>
            <pubDate>Mon, 21 Aug 2023 01:20:48 GMT</pubDate>
            <atom:updated>2023-08-21T22:35:12.568Z</atom:updated>
            <content:encoded><![CDATA[<h3>Analytics as Code — what is it, and what problems does It solve?</h3><p>In this blog post, I want to delve into the concept of Analytics as Code (AaC). Certain BI platforms now use this term to describe one of the values they offer. But what exactly is it? What benefits does it provide for you?</p><p>The idea is that by representing your analytics — data models, reports, and dashboards — as code, your engineers will be able to leverage tools and best practices that are already widely adopted in software development. This, in turn, will enable you to deploy changes more frequently and enhance both quality and automation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3mQXA9Fm0ACqFzxj" /><figcaption>Photo by <a href="https://unsplash.com/@swimstaralex?utm_source=medium&amp;utm_medium=referral">Alexander Sinn</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What is Analytics as Code?</h3><p>Let’s begin by discussing how things used to work — and in many cases, still do — before Analytics as Code (AaC) came into play.</p><h4>Before AaC</h4><p>Traditional BI tools utilized a proprietary GUI through which users configured, created, and maintained their analytics solutions. While this GUI provided an excellent user experience for most end-users, it proved impractical for engineers and maintainers, leading to increased error rates, lengthy update times, inconsistencies, duplication, and other challenges. To address these pain points, many BI tools introduced APIs that allowed engineers to automate the most common use cases.</p><h4>So what is AaC?</h4><p>AaC takes the concept a step further by enabling you to export/import and manipulate the entire analytical solution — comprising data models, calculations, reports, dashboards, and more — as code. This empowers you to harness software development tools and processes. Essentially, it allows you to create your analytics programmatically, maintain version control for your analytics using tools like GitHub or GitLab, and leverage Continuous Integration/Continuous Deployment (CI/CD) pipelines to enhance quality control and expedite delivery.</p><p>If you are not familiar with the concepts of version control and CI/CD check out these resources:</p><ul><li>GitHub on <a href="https://about.gitlab.com/topics/version-control/">what is version control</a></li><li>Geeksforgeeks on <a href="https://www.geeksforgeeks.org/what-is-ci-cd/">what is CI/CD</a></li></ul><p>It’s worth noting that this shift toward ‘as code’ is occurring in various other domains, such as Infrastructure as Code and Data as Code.</p><h4>Problems AaC is meant to address</h4><p>Let’s delve into the specific challenges that Analytics as Code (AaC) aims to tackle in more detail. It’s important to note that the true power of AaC doesn’t solely come from the ability of a BI platform to import/export a code-like representation of your analytics; it stems from decades of refinement in software development tools and best practices. These tools and processes — that can now be applied to analytics — unlock substantial value.</p><p>AaC emerged as a solution to address several challenges that managing analytics using traditional BI platforms posed:</p><ol><li><strong>Manual Configuration Complexity</strong>: In the past, building and managing analytics often relied on manual configurations through a BI platform’s GUI. This approach could lead to errors, inconsistencies, and a lack of repeatability. AaC streamlines this process, automating it to reduce the likelihood of human errors and ensure consistent and repeatable setups.</li><li><strong>Scalability and Automation Demands</strong>: With the increasing complexity of analytics solutions and the emergence of multi-tenant analytics, the demand for automation and scalability skyrocketed. Analytics as code empowers organizations to easily scale their data analytics as needed. This includes provisioning and de-provisioning environments, users, dashboards, permissions, and more, using DevOps tools to automate the process.</li><li><strong>Improving Development Efficiency and Quality</strong>: As analytics solutions grew in size, implementing changes and maintaining quality became more challenging. AaC leverages tools like Git for simplified auditing, testing, and review of changes. This not only saves time on testing but also enables quick identification and resolution of issues.</li><li><strong>Need for Reusability and Templates</strong>: Building multiple analytics solutions often involves starting from a similar base, making adjustments, and adding new components. AaC allows you to create reusable code snippets representing various parts of your analytics, such as specific chart configurations, data models, or dashboard layouts. These snippets can be easily reused or shared with others, fostering efficiency.</li><li><strong>Version Control</strong>: Traditional BI platforms often lacked robust version control and auditing capabilities. AaC integrates widely-used version control tools like Git, providing accountability, transparency, and the ability to revert to previous states when necessary.</li><li><strong>Collaboration</strong>: Collaboration and co-development capabilities varied among different BI platforms. With AaC and the use of version control tools, multiple engineers can independently develop analytics in their own environments and then seamlessly merge changes, much like collaborating on any other codebase.</li><li><strong>Analytics as Part of CI/CD Pipelines</strong>: The rise of Continuous Integration and Continuous Deployment (CI/CD) practices necessitated automating analytics provisioning and change management within deployment pipelines. AaC seamlessly integrates with CI/CD pipelines, enabling end-to-end automation. This not only enhances quality control but also ensures consistent release procedures, regardless of who operates it. This is basically what powers points 2 &amp; 3.</li></ol><p>In essence, Analytics as Code revolutionizes the management of analytics, offering improved efficiency, reliability, and flexibility while aligning with modern DevOps practices.</p><h3>FAQs:</h3><ul><li><strong>Q: If a platform supports Analytics as Code, does it mean it lacks a GUI or the GUI is not very user-friendly?<br></strong>A: No, it absolutely can have a great GUI as well — it all depends on the specific platform. Additionally, AaC is meant to help developers. BI platforms will still typically have a no-code/low-code GUI for end users.</li><li><strong>Q: I’ve heard of Infrastructure as Code (IaC) before. Is Analytics as Code similar in any way?<br></strong>A: In a way. Analytics as Code is solving similar types of problems in analytics as Infrastructure as Code solved for infrastructure management and deployment. There are many XX as Code or even Everything as Code terms being used. The idea is that you need to be able to manipulate the given thing in code to be able to scale, automate and ensure quality and efficiency.</li><li><strong>Q: Does it mean that I need to learn to code to manage my analytics?<br></strong>A: It depends on the platform you’re using. Simple tasks can often still be managed through a GUI. However, as your solution becomes more complex, coding may become necessary for efficient management.</li><li><strong>Q: Does the advent of Analytics as Code render GUIs in BI platforms obsolete?<br></strong>A: Absolutely not. Analytics as Code addresses specific pain points and challenges. GUIs in BI platforms continue to serve other needs and cater to different user personas. They are complementary rather than mutually exclusive.</li><li><strong>Q: Can you provide examples of BI platforms that support Analytics as Code?<br></strong>A: There are likely more but the two that I know of are <a href="https://www.gooddata.com/blog/why-you-should-create-your-next-analytical-project-in-code/">GoodData</a> and <a href="https://www.holistics.io/as-code/">Holistics</a>.</li><li><strong>Q: We would love to use AaC but our end users still need to be able to use GUI — how will that work?<br></strong>A: This will differ from platform to platform. For example, with GoodData one option is that you create out-of-the-box content for your end users (model, metrics, reports, dashboards) that you’ll manage through AaC and that the end users won’t be able to modify. You can though optionally allow them to create their own custom reports and dashboards which won’t be part of the AaC by default. This is a good question to ask the vendor.</li><li><strong>Q: So does AaC essentially mean that the BI platform allows you to create/export the analytics in a code format?</strong><br>A: Yes, that’s the core concept. However, different platforms may also provide various related tools to enhance the experience, such as SDKs, code editor plugins, GUI version control integration, and more.</li></ul><p>I hope this was helpful. If you have any specific questions about the topic, please don’t hesitate to leave them in the comments, and I’ll do my best to clarify!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93e9a3c179ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to learn data modeling]]></title>
            <link>https://medium.com/@terezacihelkova/how-to-learn-data-modeling-e75b351a1b37?source=rss-7307709952d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e75b351a1b37</guid>
            <category><![CDATA[database-design]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-model]]></category>
            <category><![CDATA[data-modeling]]></category>
            <dc:creator><![CDATA[Tereza Cihelkova]]></dc:creator>
            <pubDate>Tue, 25 Jul 2023 04:05:03 GMT</pubDate>
            <atom:updated>2023-07-25T04:05:03.324Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog post, I want to share with you my take on how to learn data modeling based on my own experience in the field. Before I get to tips on specific areas and resources to study, I’ll go over how I see the main data modeling phases and data model types to make sure we’re talking the same language as ambiguity sometimes exists.</p><h3>Basic terminology</h3><p>I know you probably already know these terms, but if you don’t, here you go:</p><ul><li><strong>Data</strong> is a collection of facts and statistics about the world around us, such as your height, distance to a beach, order status, or a temperature reading.</li><li>A <strong>data model</strong> is an abstract representation or blueprint that defines the structure, relationships, and properties of data we care about to help us understand it, organize it, and manipulate it.</li><li><strong>Data modeling</strong> is then the process of creating and designing a data model.</li><li>A <strong>database</strong> in the computer world, is typically a piece of software that allows us to efficiently store, retrieve, and manipulate the data. The data model defines how the data will be organized, what types of data will be stored, and how different pieces of data relate to each other within the database.</li></ul><p>And why is data modeling important? Because anywhere you want to efficiently work with data, you need a data model — not just in databases, but databases are what I’ll focus on in this post.</p><h3>Three stages of data model design</h3><p>When it comes to data modeling, there are three frequently discussed stages — or levels of abstraction — in data model development:</p><ol><li><strong>Conceptual data model </strong>— a non-technical, high-level description of relevant entities and relationships.</li><li><strong>Logical data model</strong> — includes more details, such as attributes we want to track for each entity. Still business-friendly.</li><li><strong>Physical data model </strong>— a database-specific model that governs how the data will be stored.</li></ol><p>In simpler terms, it progresses from: “We’ll have customers buying products in our great new app” (conceptual) to “Each customer can buy multiple products, and each product can be bought by multiple customers. Also, Customer ID uniquely identifies each customer…” (logical) to “Customer ID will be an auto-incrementing integer because that’s what works best with the database XY” (physical).</p><p>All these models can be captured and documented in various ways, but one of the most frequently used is an Entity Relationship Diagram (ERD).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ov9kyT3F8Vh58HekwKfMaQ.png" /><figcaption>Example of evolution of an ERD diagram for a simple order system</figcaption></figure><p><strong>Note: What is a semantic model?</strong></p><p>A popular term nowadays is the semantic model. The details may vary vendor by vendor, but it’s a flavor of a logical data model meant to abstract users from the complex and technology-specific physical model. For example, the analytics platform <a href="https://www.gooddata.com/headless-bi/">GoodData</a> offers a semantic model/layer that the end-users — oftentimes business users — can interface with and build analytics on top of without worrying about the complexities of the underlying physical data model. There is much more that could be said about it, but I’ll leave that for another blog post — let me know if you‘d like to learn more!</p><h3>How technical do you need to be?</h3><p>In the initial stages of data model development, you don’t need to have a deep understanding of databases. What is more important at that point is that you have great communication skills, can facilitate data discovery sessions with business owners, and understand the business rules. Only when you get to the level of the logical model should you have some measure of understanding of the different modeling techniques related to different types of data applications (e.g., transactional database vs. data warehouse), and definitely at the physical data model level, you have to be an expert on the selected database.</p><p>That said, when you have small teams, oftentimes all levels of the modeling are handled by the same person, and some stages can be skipped or at least not formally documented.</p><p>For the purpose of this blog post I’ll assume you want to be able to do the data modeling end to end.</p><h3>Types of data models</h3><p>Apart from the different phases of the data model design (conceptual, logical, physical), there are also different types of models based on use case and technology.</p><h4>Different use cases</h4><p>When developing your data model, you have to know what it will be used for. Will it be used to store application data for an eShop? Will it be used to perform data analytics on top of your company’s data from various data sources? Will it be used to support navigation and help find the best paths between locations? Based on the use case, you’ll pick a different data modeling approach and technology.</p><p>Two very frequently used approaches to data modeling are (although there are many more):</p><ol><li>Transactional data (<strong>OLTP</strong>) — is a type of database processing that focuses on managing and executing high volumes of real-time transactional operations efficiently. For example, storing data for an eShop. The most frequently used data modeling approach here is called the <strong>3rd normal form</strong>.</li><li>Analytics data (<strong>OLAP</strong>) — is a type of database processing that focuses on analyzing large volumes of historical data to support complex business intelligence and decision-making tasks. The most frequently used data modeling approach here is called <strong>dimensional data modeling</strong>.</li></ol><p>At the latest, at the logical data model level, you’ll have to take into account the selected data modeling approach.</p><h4>Different types of databases</h4><p>Most databases are meant to be used for specific use cases. Some store data in tables, some store data as documents, some store data as graphs, some as key-values, etc. Some databases scale better, some support many concurrent users accessing the data at the same time, some are better for frequent writes, some are better for running complex queries, etc.</p><p>In short, based on your use case, you’ll narrow down the list of databases that support it well. You might still be left with a large number of databases that, for example, support data analytics and can handle concurrent users (if those are your requirements). You can then narrow down the list further based on pricing, etc.</p><p>The database you select will then have an impact on the physical data model design. The logical data model should ideally look the same no matter which specific database you’re using.</p><p>There are two terms I have to mention here as you’ll run into them soon and frequently. At a high level, people categorize databases as either <strong>relational databases</strong> or <strong>NoSQL databases</strong> (that is how all databases that are not relational databases are called). The concept of a relational database is very old and still massively used. Relational databases are the databases with tables that store structured data, which you can query using SQL query language, and you’ll probably find at least one of them in every company. Examples might include MySQL, PostgreSQL, Snowflake,…</p><p>NoSQL databases came around to help us work with large volumes of semi-structured and unstructured data. Examples are MongoDB, Redis, Couchbase,…</p><p>There are many subtypes of NoSQL databases — graph, document, key-value store, and others.</p><p>Ok, I think that’s enough about terminology… uff. Feel free to comment if something doesn’t make sense to you or if you think about it differently.</p><h3>What to learn?</h3><p>Now you know that there are three commonly recognized data models based on the stage (conceptual, logical and physical) and that you don’t need to be very technical to work on the conceptual models, and possibly might also wing a logical one, but you do need to be very technical to design the physical data models.</p><p>In some companies, you’ll have different roles that work on different levels of the data model — for example, you might have a business analyst or data architect working on the conceptual and logical data model while a data engineer works on the physical model. In other companies, it will be the same person doing all three.</p><p>You also know that the logical data model varies based on the use case (e.g., transactional data vs analytics) but shields you from the specifics of the selected database. The physical data model is designed based on the specifics of the selected database.</p><p>Assuming you want to eventually be able to tackle all three levels of data model design, this is where I’d recommend you start:</p><ol><li><strong>Basics of computer and cloud architecture: </strong>how is data stored and processed by computers and moved across networks. At least have a basic idea before you move forward.</li><li><strong>Database Fundamentals</strong>: Understand the basics of databases, how they are structured, and the different types of databases and their uses (relational, NoSQL, etc.).</li><li><strong>Dive into relational DBs</strong> (great start unless you already know you want to do something else):<br>- Learn to use a database (manipulate and query data using SQL).<br>- Learn the principles of data modeling for transactional databases (3rd normal form). You can learn the basics from the book <strong>“Database Design Solutions” by Rod Stephens.</strong><br>- Learn the principles of data modeling for analytics (dimensional data modeling). A good book, even though a bit old, is <strong>“Star Schema The Complete Reference” by Christopher Adamson.</strong></li><li><strong>Pick a technology</strong> (specific DB) and deep dive into that. If you don’t have a specific use case you want to focus on, go for one of the <a href="https://survey.stackoverflow.co/2022/#section-most-popular-technologies-databases">most used databases</a>.</li><li>Optionally, if you’re interested in a specific industry, <strong>research examples of data models for the industry</strong>. There are tons of examples of data models for fintech, eCommerce etc.</li><li>A little bit out of order but very important and hard to teach would be <strong>business requirements analysis. </strong>Basically, learning how to gather and analyze business requirements to ensure the data model aligns with the organization’s needs.</li><li><strong>Data Security and Privacy</strong>: Understand the importance of data security and privacy regulations to design secure and compliant data models.</li></ol><p>If you’d like to get somebody else’s list of resources check out this <a href="https://dataengineering.wiki/Learning+Resources">curated list of books and courses from a data engineering Reddit community</a>.</p><p>Whatever you do try not to get stuck in a tutorial hell :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WIav5fjZe0vw0wfN" /><figcaption>Photo by <a href="https://unsplash.com/@picsbyjameslee?utm_source=medium&amp;utm_medium=referral">James Lee</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Summary</h3><p>I hope this gave you some idea on where to start. One more thing I want to note is that data modeling doesn’t exist in a vacuum. Frequently it is a part of data management or data engineering roles. Some nice books that cover more than data modeling are:</p><ul><li>“Fundamentals of Data Engineering” by Joe Reis and Matt Housley</li><li>“Designing Data-Intensive Applications” by Martin Kleppmann</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e75b351a1b37" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>