<?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 BlankaK on Medium]]></title>
        <description><![CDATA[Stories by BlankaK on Medium]]></description>
        <link>https://medium.com/@blanka_49545?source=rss-890f31d3a139------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JNNHx8Mm8nUj87lgsqi_ug.jpeg</url>
            <title>Stories by BlankaK on Medium</title>
            <link>https://medium.com/@blanka_49545?source=rss-890f31d3a139------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:27:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@blanka_49545/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[The Quiet Relief of Asking Dumb Questions Again]]></title>
            <link>https://medium.com/@blanka_49545/the-quiet-relief-of-asking-dumb-questions-again-a2e77fcb60eb?source=rss-890f31d3a139------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2e77fcb60eb</guid>
            <category><![CDATA[professional-learning]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[ai-assisted-learning]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[BlankaK]]></dc:creator>
            <pubDate>Wed, 22 Apr 2026 06:55:51 GMT</pubDate>
            <atom:updated>2026-04-22T06:55:51.341Z</atom:updated>
            <content:encoded><![CDATA[<p>Professional life is full of things we’ve quietly stopped asking about. With AI assisted learning, we’ve got a great opportunity to get some of it back.</p><p>I remember what it felt like to learn at university. Not the content, most of that is long gone, but the mindset of it. You showed up explicitly to not know things. Asking a question in a tutorial, even basic ones, was the whole point. Nobody was billing hours. Nobody was thinking about getting promoted.</p><p>Something happens to that mindset when you enter a profession. It doesn’tt go away overnight, but it quietly erodes as titles go from junior to senior. Asking questions, that once felt natural, can feel a decade later like a small professional risk.</p><h4>When Curiosity Becomes a Cost</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kXIu_5HdyBNGu2WkbPA0qA.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@picasjoe/">Picas Joe</a> on <a href="https://www.pexels.com/photo/time-and-money-11348123/">Pexels</a></figcaption></figure><p>Some of it is simply the nature of the job. At university, understanding something deeply was the deliverable. In a profession, it’s just a stepping stone, and potentially a slow one. You learn because you need to produce, and that reframes your relationship with not knowing. To some extent curiosity becomes a cost, not a virtue.</p><p>Partly it’s the various roles we take on as professionals. Today my colleague is a teacher, tomorrow we’re peers on the same project, arguing for different approaches to a problem. The “face” I’ve lost in one context doesn’t go away just because we’ve switched meeting rooms.</p><p>Then there’s the question you’ve already asked. As someone who’s worked with hourly billing for the better part of a decade, there’s nothing I hate more than wasting people’s time. Asking the same question twice, because the answer wasn’t written down the first time, is something I avoid doing, and expect the same from others. And before you even get to the question, there’s the setup: reconstructing the context for whoever you’re asking, getting them up to speed before they can help you. It’s a small tax, but it adds up.</p><h4>Enter the AI Teacher</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KMKl_ii9aQi52fGgl-SRug.png" /><figcaption>Photo by <a href="https://unsplash.com/@mekanizm">Justin Ha</a> on<a href="https://unsplash.com/photos/ER3BuRKBJ2g"> Unsplash</a></figcaption></figure><p>And then I started using an AI assistant for coding, specifically Claude Code. Judgement free, no hourly rate, no memory of the question I asked last week. I didn’t realise how much I’d been quietly censoring my own curiosity until I suddenly didn’t have to. Now, don’t get me wrong, I have the best co-workers I could ask for, a genuinely safe space. But even there, I feel better not wasting their time with “what does sudo do?” or “how do I navigate the filesystem?”. Instead we get to talk about more complex issues and fundamental ideas behind the code.</p><p>Part of what makes this work so well is the proximity. No window switching, no context loss, just a conversation happening directly alongside my code, with changes appearing in my editor in real time. I’ve only experienced this with Claude Code, but I’d be surprised if the principle didn’t hold elsewhere, whether that’s another coding tool or learning something else entirely.</p><h4>Full circle</h4><p>At university, curiosity was the whole point. Somewhere along the way it became a liability, not because I got lazier, but because the environment made it costly in more ways than one. What surprised me about AI-assisted coding wasn’t the productivity gain. It was getting the learning mindset back, in a context where I’d stopped expecting to find it at all. That’s not a small thing. The tools that help you produce are everywhere. The ones that also let you think out loud, without consequence, are rarer than they should be.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2e77fcb60eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A New Tapestry: Exploring Microsoft’s Fabric in Analytics]]></title>
            <link>https://medium.com/@blanka_49545/a-new-tapestry-exploring-microsofts-fabric-in-analytics-f588deaae962?source=rss-890f31d3a139------2</link>
            <guid isPermaLink="false">https://medium.com/p/f588deaae962</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[power-bi]]></category>
            <category><![CDATA[microsoft-fabric]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-driven]]></category>
            <dc:creator><![CDATA[BlankaK]]></dc:creator>
            <pubDate>Tue, 05 Dec 2023 14:51:43 GMT</pubDate>
            <atom:updated>2023-12-05T14:51:43.606Z</atom:updated>
            <content:encoded><![CDATA[<p>Thoughts from an Analytics Engineer</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/216/1*cEUa9M3-hDKd-ish-mT-7w.png" /><figcaption>Microsoft Fabric logo</figcaption></figure><p>MS released its concept Fabric just as we were all getting ready to check out for the summer. The excitement was high but the reasons were unclear to me. I’ve since tried it out and this post is my take on what it is and why it could be considered exciting. I’m basing it on the experience I’ve gathered since joining the analytics field about 1.5 years ago, having worked mainly in maintenance and support, primarily in a solution consisting of power BI sitting atop a dbt transformation layer. Let’s dive in and see what synergies come with this unification.</p><h3>Basics: what is MS Fabric?</h3><p>MS has set out to create a “one-stop-shop” for the whole analytics stack, bringing together the following tools under the same umbrella:</p><ul><li>Power BI — dashboarding</li><li>Azure Data Factory — ingestion and data pipelining</li><li>Synapse Data Engineering — data processing via eg. spark</li><li>Synapse Data Science — wrangling and ML capabilities via eg. Spark, Python</li><li>Synapse Data Warehouse — storage</li><li>Synapse Real-Time Analytics — real-time processing and analytics</li></ul><p>The tools cover the whole process, from data ingestion and transformation to data science, visualization, and real-time processing and alerting. However, most of these features are already existing MS products, such as Azure Data Factory and Power BI, but now they’re packaged seamlessly with a unified UI — similar to when Excel+Word+etc was packaged into Office.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*HXfXxsUFSEfOyNkPbL5YTA.png" /><figcaption>Image by Author using MS logos and excalidraw showing the packaging of MS tools to Fabric</figcaption></figure><p>From the front-end perspective, the cool thing is that it looks like Power BI can be plugged in anywhere in the data flow. It can sit right above ingestion, on a real-time stream, atop data science stuff — the possibilities are endless. Which brings me to:</p><h3>Unification → efficiency</h3><p>With the various tools being well integrated through the unified interface, data isn’t moving around between various tools. When data enters the fabric universe, it gets converted to an efficient format (delta and parquet) and gets put in the Onelake, a metaphorical equivalent to OneDriva for datasets. After which, it doesn’t move. It can be used in the various faces of fabric, without leaving the comfort of the lakehouse, meaning no copying, and in some instances dedicated datasets that need to be reloaded.</p><p>Furthermore, with one source of data, there’s only one security and governance system, and perhaps most importantly, one pricing model. Fabric is being sold per Capacity Units (CUs), with computing power moving between components as needed, which is a very straightforward model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zVVM9-TVLUFwiOY3ELa5qQ.jpeg" /><figcaption>Generated using Bing Image Generator — powered by DALL-E 3 [prompt: Unification of data tools illustrated minimalistically, nature theme with a tree]</figcaption></figure><h3>Traceability?</h3><p>My one reservation, being a dbt spoiled brat working in maintenance, is regarding traceability. When end users come in with questions of the form “the number in the dashboard doesn’t look like the number in my source system?!”, dbt provides excellent lineage documents where you can see how various tables are connected and what transformations and joints are performed, an example of which is shown in the image below. This allows you to trace data fields all the way from an output layer down to the source through a web interface, instead of having to open various SSIS packages or similarly set up solutions. From what I’ve seen of fabric, that is not readily available, or at least not clearly available. This is a shame as it would be neat to see how a data field flows through the various components. But maybe that’s coming later — maintenance is rarely considered “cool” and advertises loudly in a first release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nMQE1tzodzh0t2ftMEhgcQ.jpeg" /><figcaption>Example of dbt generated DAG lineage, source: <a href="https://docs.getdbt.com/terms/data-lineage">https://docs.getdbt.com/terms/data-lineage</a></figcaption></figure><h3>Conclusion</h3><p>MS have created a one-stop-shop for analytics. With the unified UI and straightforward pricing model, I think the simplicity of the system is really what’s going to hit big, with nontechnical stakeholders being able to understand and interact with the system and get into the nitty-gritty of it. What can be questioned is if the provided components of fabric are better than components provided by a supplier just focused on one thing, parallel to the “don’t buy hiking boots from North Face that tries to make everything, buy it from Hanweeg who specializes in shoes”. But then again, integration is not a thing with shoes so the argument might be invalid.</p><p>Overall, I’m very excited to see this implemented on a larger scale! Getting all these chefs to cook up soup IN THE SAME KITCHEN is going to be very interesting to see and be a part of!</p><h3>Dive in</h3><p>To take a closer look into this topic, here are some links that I found useful to get an overview of fabric:</p><ul><li><a href="https://learn.microsoft.com/en-us/fabric/get-started/microsoft-fabric-overview">https://learn.microsoft.com/en-us/fabric/get-started/microsoft-fabric-overview</a></li><li><a href="https://www.youtube.com/watch?v=J3Z7SNqdhdY">https://www.youtube.com/watch?v=J3Z7SNqdhdY</a></li><li><a href="https://learn.microsoft.com/en-us/training/paths/get-started-fabric/">https://learn.microsoft.com/en-us/training/paths/get-started-fabric/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f588deaae962" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>