<?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 Ana on Medium]]></title>
        <description><![CDATA[Stories by Ana on Medium]]></description>
        <link>https://medium.com/@eyeofdata?source=rss-9025307ec859------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2LR076GPq9VmGZ2BUZ3ZKw.png</url>
            <title>Stories by Ana on Medium</title>
            <link>https://medium.com/@eyeofdata?source=rss-9025307ec859------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:47:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eyeofdata/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[Data analysis and visualisation of The Simpsons from beginning to end]]></title>
            <link>https://medium.com/hackernoon/the-simpsons-seasons-ratings-d516d748b1f5?source=rss-9025307ec859------2</link>
            <guid isPermaLink="false">https://medium.com/p/d516d748b1f5</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[the-simpsons]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Ana]]></dc:creator>
            <pubDate>Thu, 22 Feb 2018 13:28:35 GMT</pubDate>
            <atom:updated>2018-02-27T17:42:22.994Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*96j0EZOiFmH0E0ujzihV8w.png" /></figure><p>So far, I have been posting only visualisations I had already created, most of them at work. This time, I created something specific for the blog as I wanted to see if I could do a video of the whole process — analysis of the data, basic plot, final and edited plot. I warn the readers, that video recording and editing for me is something completely experimental and out of my regular skill use. Any feedback is appreciated and I will make sure to improve as I keep on doing these posts.</p><p>While thinking about recording this video, I browsed kaggle.com in search of a fun dataset to work with. I came across a couple of datasets from The Simpsons and ended up choosing one named <a href="https://www.kaggle.com/wcukierski/the-simpsons-by-the-data">“The Simpsons by the Data”</a>. It contained 4 .csv files: simpsons_characters.csv, simpsons_episodes.csv, simpsons_locations.csv and simpsons_script_lines.csv.</p><p>For this post, I analysed only the file simpsons_episodes.csv, which contained the following variables: <em>id</em>, <em>title</em>, <em>original_air_date</em>, <em>production_code</em>, <em>season</em>, <em>number_in_season</em>, <em>number_in_series</em>, <em>us_viewers_in_millions</em>, <em>views</em>, <em>imdb_rating</em>, <em>imdb_votes</em>, <em>image_url</em> and <em>video_url</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ddd1ukzghZsh1xwapVsR3A.png" /><figcaption>part of the simpsons_episodes.csv in an R dataframe</figcaption></figure><p>One thing that is missing in the video is that the first time I loaded the file into R, I noticed that the dataframe had 298 lines instead of the 600 it was supposed to have. When looking at the dataframe in RStudio, I noticed that one line had a quotation mark that wasn’t closed, which didn’t allow the data to be loaded correctly. I removed this quotation mark by hand because it was just the one, but normally, data cleanup should be done programatically as to be easily repeatable.</p><p>The video shows a really basic analysis on R of some of the variables, a construction of a plot and then the plot enhancement on Adobe Illustrator. In the video I also explain my train of thought and why I chose to so certain things. Check it out!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F5jFluFh8qPY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D5jFluFh8qPY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F5jFluFh8qPY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e2d80a28fe16bf8ece8fd06891319bdb/href">https://medium.com/media/e2d80a28fe16bf8ece8fd06891319bdb/href</a></iframe><p>Here is the plot created on R and edited on Adobe Illustrator (before and after).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gE_z4uSOBXAx3mGye8D_KQ.png" /><figcaption>IMDB rating of The Simpsons seasons (before and after editing)</figcaption></figure><p>As mentioned in the beginning, this is something completely new. Let me know if you enjoyed it, what topics you’d like to see me talk about or do videos on and I will try to make more content!</p><p><em>Edit</em>: link for code used in the video -<a href="https://gist.github.com/anabarbosa/3dccb842c1d0a3cfd547ee90b508a19a">https://gist.github.com/anabarbosa/3dccb842c1d0a3cfd547ee90b508a19a</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d516d748b1f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/the-simpsons-seasons-ratings-d516d748b1f5">Data analysis and visualisation of The Simpsons from beginning to end</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Password Analysis]]></title>
            <link>https://medium.com/hackernoon/password-analysis-7a8181185143?source=rss-9025307ec859------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a8181185143</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Ana]]></dc:creator>
            <pubDate>Thu, 08 Feb 2018 11:37:06 GMT</pubDate>
            <atom:updated>2018-06-14T17:57:22.699Z</atom:updated>
            <content:encoded><![CDATA[<p>In late 2016, two databases containing millions of credentials were made public — AntiPublic Combo List and Exploit.in Combo List. These databases contain a combination of usernames/ email addresses and passwords from different online services.</p><p><a href="https://binaryedge.io/">BinaryEdge</a> presented me with the chance to do a full analysis on the content of these databases. The idea was to gather all passwords presented in both lists and analyse them in order to extract significant statistics.</p><p>This was a particularly challenging project for me as I had never done password analysis before.</p><p>Although the analysis has already been described in <a href="https://blog.binaryedge.io/2017/07/24/antipublic-password-analysis/">BinaryEdge’s blogpost</a>, this post is more focused on the processes I used when creating visualisations to present the statistics found. I’ll take a couple of examples from the many that were presented there.</p><p>So, first things first, I did some research on what was known about these lists. At the time (early 2017), not much was known about them (apart from the content) or where they had come from.</p><p>My first thought was “ where do I even start?”. After checking the size of the files I was dealing with, I did a basic analysis to check the number of lines the files had, which of those were unique, how many email addresses, passwords and usernames were presented on these lists. This was the easy part. I then went on analysing emails and passwords separately.</p><p>Although the analyses on both databases were done independently, I wanted to present the results together — the way I thought this worked best was by using colours that represented each one, maintaining consistency throughout the visualisations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*g_bfn1ZL1xbjjgDYbFHJ1Q.png" /><figcaption>color labels present in all the designs</figcaption></figure><h4>Email addresses</h4><p>Analysing email addresses wasn’t part of the original assignment but, out of curiosity, I ended up analysing them aswell. This analysis gave me information on domains and TLDs (top level domains, such as .com).</p><p>The figure below represents the domains present in the databases analysed. For me, it was quite important to give some kind of emphasis to the most prominent numbers (yahoo numbers in this case) and, once again, I thought that color would be a good choice here as readers are redirected to that box instantly.</p><p>One of the difficulties I had with the results was that the they were a bit skewed, which means that it wouldn’t look good in a regular plot — the smallest values wouldn’t be readable. An alternative to this could be to use a scale break, or broken y axis, or maybe plot it twice — one plot with the largest values and the other plot with the smallest values. For me, it made more sense not only to use percentages instead of the values, as it makes it easier to compare them, but also to create an alternative representation as seen below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*6Xfi2UgMzcBuaUfEAifLJQ.png" /><figcaption>data visualisation design created in Adobe Illustrator</figcaption></figure><p>A small detail that I think makes all the difference is that little black and white box on the top. I always add something that somehow guides the reader and makes it easier for him to understand what the he’s looking at. In this case, the box let’s you know that the percentages you’re seeing there are the domains in the complete database.</p><p>I actually haven’t looked at these figures since we published them. While writing this post, I took my time to look at them again and came to the conclusion that if I had done this today, I wouldn’t do it exactly the same way.</p><p>For instance, I remember thinking at the time that such a high number of yahoo.com email addresses (the box on the right) should be mentioned here as it was an important piece of information. However, I realise now that this could have been included in the blogpost itself and didn’t necessarily had to be in the figure.</p><p><a href="http://thesprawl.org/projects/pack/">PACK (Password Analysis and Cracking Toolkit)</a>, a great tool for extract statistics on passwords, was used to analyse passwords’ lengths — the result was a CSV file with the length of the passwords and the number of times they were found. Then, I loaded this data in Microsoft Excel and created the plot below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y5wmHPMMCDQME9h3xv7kWg.jpeg" /><figcaption>exploit.in — password length plot</figcaption></figure><p>In this specific case, I chose to use a simple tool as Excel, as I knew I wanted to add a couple more details to my design. So, by loading the data into Excel, I just had to draw a basic plot and export it.</p><p>Please note that the plots that are created with any tool, be it Microsoft Excel, R or Python for example, could and should look a lot better than the one above — they should at least have a title and labels on both axis. In this specific case, I knew I wanted to add a couple more details to it, so I went with the most basic plot. The figure below is the final design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q_Nim7IRha5Qccz7WfyJWg.png" /><figcaption>final design</figcaption></figure><p>The examples I’ve been showing you (in this and previous blogposts) have been drawn in Adobe Illustrator. However, a good idea is to do the data analysis in R (for example) and create a basic plot there. Then you can export that plot and clean it up in Adobe Illustrator. This is what I did when analysing the length of the passwords present in the combo lists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fRKA1yYI7Q0YLCk23tdStg.png" /><figcaption>step-by-step plot clean up in Adobe Illustrator</figcaption></figure><p>My thought here was to include some notes on the most relevant data points in order to simplify the process of comparison between the results of both databases. It isn’t necessary to add these details all the time but in this case it made sense as we were comparing two different databases and the plot had a very similar shape. For instance, without the labels on the most relevant datapoints, I think it would be very difficult to compare both graphs.</p><h4>Conclusion</h4><p>In summary, every visualisation should be independent from the others (each one has its one color guide), it should have all the information needed for the reader to interpret it without having to constantly go back. But, in the end, the most important idea is to make it as easy as possible for someone to interpret your design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a8181185143" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/password-analysis-7a8181185143">Password Analysis</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What data visualisation has taught me so far]]></title>
            <link>https://medium.com/hackernoon/what-data-visualisation-has-taught-me-so-far-daf750dcfbab?source=rss-9025307ec859------2</link>
            <guid isPermaLink="false">https://medium.com/p/daf750dcfbab</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ana]]></dc:creator>
            <pubDate>Fri, 26 Jan 2018 17:57:07 GMT</pubDate>
            <atom:updated>2018-01-26T17:57:07.486Z</atom:updated>
            <content:encoded><![CDATA[<p>Since I dived into data visualisation I’ve learned so much that sometimes it’s difficult to explain every little detail. So I thought I’d start by writing about the fundamentals of making a good and accurate visualisation I’ve gathered so far. I’m writing this for everyone that might be interested in this topic and, as me, is still in the beginning.</p><p>Most of the fundamentals of data visualisation I learned from the books I mentioned in <a href="https://medium.com/@eyeofdata/eye-of-data-the-beginning-ac4ff57a164">my previous post</a>.</p><p>There are many different definitions of what data visualisation is. In his book “Data Visualisation: a successful design process”, Andy Kirk defines Data Visualisation as:</p><p>“<strong><em>a multidisciplinary recipe of art, science, math, technology, and many other interesting ingredients.”</em></strong></p><p>I know every person has its own take on this topic but, to this day, this was the definition that really got stuck with me.</p><p>Getting the definition right is the easy part. Creating something meaningful that inspires other people and addresses the information accurately is the hard part. There have been many times where I created visualisations and infographics that when looking back, I would have changed certain aspects and some I even chose not to use.</p><p>But I think the most important thing I’ve learned so far is that your work never actually goes to waste— even if a design you created doesn’t work for the purpose that you created it, it doesn’t matter — sometimes you’ll end up re-using some of those designs in the future, or maybe they will be of use as inspiration for some other work.</p><p>If you have the time, make sure you read Andy Kirk’s book “Data Visualisation: A Handbook for Data Driven Design” as well as Cole Nussbaumer Knaflic’s “Storytelling with Data”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EN9IF_wNxtOj7Yk5GLAJTQ.jpeg" /><figcaption>two of my reference books</figcaption></figure><p>As Nadieh Bremer explains in <a href="https://www.superdatascience.com/data-visualization-training/">her interview in the SuperDataScience podcast</a>, the most important step is the question. You have to have a specific question about the data that you want answered both with your analysis and your visualisation. This is the first step.</p><p>In the beginning, I wasn’t used to paying much attention to the details in a graph, plot or figure. There are tiny details that we don’t notice until they are missing. Consider the images below, which were created for <a href="http://ise.binaryedge.io/">BinaryEdge’s 2016 Internet Security Exposure Report.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0adcl9j9YuaMCKJtE_aTNQ.png" /><figcaption>bad vs. good visualisation</figcaption></figure><p>In my opinion this is a good example of what I was mentioning above — the details make all the difference. You can see that although both figures are based on the same data, the way they are presented is significantly different.</p><p>One of the most basic components the graph, figure, infographic or visualisation you’re designing should have <strong>a title</strong> (and maybe a subtitle) to a graph, figure, infographic or whatever you’re designing. This is the first piece of information that the reader will be drawn to. Looking back, I realise now that I should’ve added a subtitle that added a bit more context to the image, such as “number of IP addresses with the 10 most common SSH banners”.</p><p>Then, it’s fundamental to <strong>lead the reader through your work</strong>. For instance, maybe you noticed that the image on the right has a small label on top indicating that we’re looking at SSH banners (already said in the title) and that the numbers are a count of the IP addresses with those banners. Of course, the level of detail in which you describe your design is highly dependable on how the information is going to reach your audience, so you should add as many guidelines as necessary that they can understand your work without you.</p><p>Independently of the tool you use to create your design, make sure it is precise. Having <strong>precision in design</strong> makes a huge difference in the final result of your work. Don’t forget that your design will end up representing you, so you want to be sure that you’re precise and methodical with your work. For example, in the image below, the area of each circle is proportional to the data associated with it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yrL5N2Q7oPsFkzhKjC04tw.png" /><figcaption>notice how the markers indicate both location and quantity</figcaption></figure><p><strong>Note:</strong> When using the area, be aware that the difference between the squares isn’t as easy to distinguish visually as it would be if, for instance, length was used (and this is one thing that could’ve been done differently in this example).</p><p>Another important point you want to be careful with when creating data visualisations, infographics or even presentations is to <strong>make them engaging</strong>. This means, removing everything that is not relevant but making sure that the key information is kept. Of course that having a beautiful design is very important but, for example, if you have something in your design that is only there to make it pretty, maybe it shouldn’t be there at all as it is taking not only space but also the reader’s attention.</p><p>There are also some extra <strong>details that are worth paying attention to</strong>.</p><ul><li>The <strong>composition</strong> of your design is key — don’t just throw stuff in a blank page, make sure it is arranged as best as possible.</li><li>Choosing a <strong>good font</strong> makes all the difference — avoid the use of fonts such as Times New Roman or Comic Sans as they look a bit careless, transmitting the wrong idea to your audience and choose fonts that are easy to read.</li><li><strong>Colour</strong> shouldn’t be used only to embellish your work — it should have a functional purpose. For instance, it can be used to accentuate a certain detail. In the image above, the colour saturation was used make it easier for the user to differentiate between the higher and lower numbers.</li></ul><p>Finally, I have to mention <strong>storytelling</strong>. Storytelling is all about communicating efficiently with your audience, give them context to what they’re seeing/ reading and put yourself in their shoes. You have to consider the audience’s profile (who you’re targeting) and what is the most relevant and interesting information for them. In a future blogpost I intend to talk more in detail on this topic and show you some examples</p><p><strong>I created this small reference card for guidance (yours and mine)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dBNRAvN7WmHwKij8GB-tFg.png" /></figure><p>All of these concepts are fundamental to keep in mind when creating a data visualisation piece or any other form of disseminating information. Some of them are easy to understand but more difficult to put into practice. I speak for myself of course when I say that sometimes I am so deeply focused on the data and how to represent it that I forget to pay attention to all this tiny details. Only later, when I go back and analyse my design again is when I realise that a few key “ingredients” are missing.</p><p>This is only a small summary of the key ideas I took from the amazing books I mentioned above.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=daf750dcfbab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/what-data-visualisation-has-taught-me-so-far-daf750dcfbab">What data visualisation has taught me so far</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eye of data — the beginning]]></title>
            <link>https://medium.com/@eyeofdata/eye-of-data-the-beginning-ac4ff57a164?source=rss-9025307ec859------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac4ff57a164</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Ana]]></dc:creator>
            <pubDate>Mon, 22 Jan 2018 12:19:43 GMT</pubDate>
            <atom:updated>2018-01-22T12:19:43.120Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*QNAILfq_DLtviIiaCQRndQ.png" /></figure><p>Since I can remember it, I wanted to be a pharmacist.</p><p>I loved chemistry, math and working in a laboratory. I was really passionate about it. I could do these things all day and it would be a great day.</p><p>As I enrolled in my Master’s Degree in Pharmaceutical Sciences, it took me a while to realise that maybe I wasn’t going to be able to spend everyday in the lab working on experiments or just with my head buried in a complex chemistry problem. However, the more I progressed in the course, I started to realise that it wasn’t what I really wanted.</p><p>Even though I still loved the same stuff, everything that I was learning was leading me more to selling medicine in a pharmacy rather than doing experiments. It wasn’t what I wanted to do at all.</p><p>By the time I was finishing my degree, I was really demotivated.</p><p>I still finished and was really happy not only about it but for the great people I met at the University and everything else I learned. But I knew that working in a pharmacy wasn’t something that I wanted to do on the long run.</p><p>I was, by luck presented with the opportunity to work at a company as an administrative assistant. I did know again that I wasn’t going to do this forever but I was really excited about the job, the company itself, its values and the team I would be working with. I was pretty happy watching the company grow and even myself as I had the chance to learn a bunch of new stuff and work with different mindsets and values.</p><p>However, it came to a point that I felt that I needed something else.</p><p>I needed something challenging. That was when it was suggested to me that I could learn how to code. I didn’t have any programming experience, so I pretty much had to start from scratch. I tried it first with Python, then with R. It wasn’t easy at times, but it was exactly what I wanted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*U6p3h5q96OWnVxvbYPMi8Q.jpeg" /><figcaption>Me typing my first few lines of code…</figcaption></figure><p>I started to do data analysis using company’s data and I loved it.</p><p>I could spend hours working on it. And it wasn’t just about writing a few lines of code — it was about figuring out what the data was hiding and what knowledge we could extract from it.</p><p>A couple of months into this, I started to play around with Adobe Illustrator. From an early age that I loved to draw and paint. I wasn’t really good at it, but it was something I enjoyed doing in my free time.</p><p>So it’s easy to guess what was the next step for me right?</p><p>I started to read a lot about data visualization techniques, doing research on the topic and spending hours trying to make sense of the visualizations I was looking at. I learned that every one of them was so much more about a story than just numbers. This was really exciting for me. Of course I had come across many graphs and different designs my whole life, but I didn’t spend much time thinking about them — I took the information that was useful for me and that was it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zFsit_21-jM0zoB9wlUgPg.jpeg" /><figcaption>Part of my book collection</figcaption></figure><p>I was really inspired by the work of David McCandless, Alberto Cairo, Isabel Meirelles, Nathan Yau and Andy Kirk, just to mention a few. I learned so much from their books and work in general.</p><p>This first post, might be meaningless for some people that from young knew the career path they were going to follow, but maybe it will help others that had the same experience as me and changed to a career they felt was a better choice for them.</p><h3>So what is Eye of Data?</h3><p>I created this page to put into words what my train of thought is every time I am presented with a piece of data and try to create something meaningful and useful for other people to understand that data.</p><p>My learning process didn’t start that long ago, I’m still quite in the beginning but I want to keep improving what I do. Some of my ideas are not that great while others end up working, but I won’t be posting here only the good ones. Anyway, it would be great if I could have some feedback out of this.</p><p>When I first tried to design a logo for this page, I didn’t have a clear picture of how it should look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E-c6pXEV58djMiBZ16ASDg.png" /><figcaption>First draft on paper</figcaption></figure><p>I knew the idea it should transmit though — I wanted it to represent how the data is in its raw presentation and how, going through the data cleaning process, filtering and data visualization, it is transformed into something clean, beautiful, well presented and easy to understand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l3HabFVdT-jr7pAUpfjThw.png" /><figcaption>eyeofdata logo design process</figcaption></figure><p>So my line of thought was that the little squares on top, all in different angles, all disorganised would represent unstructured, raw data. The lamp would represent the ideas and the thinking process going on while analysing the data. And finally, the organised squares inside the lamp would be the output, the structured data.</p><p>I will regularly update this page with two types of content:</p><ul><li>One in video format where I do a “quick drawing” on how I build a piece of data visualization.</li><li>A normal medium post, where I analyse in written format a visualisation.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac4ff57a164" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>