How I optimized my learning time with Instapaper

How I optimized my learning time with Instapaper


I am not a huge book reader, but I read a ton of different articles on the internet. They cover multiple topics like Power BI, SQL Server, DAX, Running, World news, High Tech review, Blogging, Self-improvement, and many other topics I want to cover at a specific moment. (Now, everything related to my house, design, …)

When I browse LinkedIn or Twitter, I find interesting articles, but sometimes I do not have time to read it. (Or maybe I am not in the mood to read them right now).

I also have a big trouble (and it seems that I am not the only one on earth). On a computer or a smartphone, my focus time is quite small. I like to switch between applications and topics, which decreases completely my learning curve. You know this little monkey in your head who tries to discourage you to finish something he thinks “too serious for him”.

On this topic, I kindly recommend you to watch this TED video:

I found a solution to solve that problem, and it is a technical solution which provides me much more fun.

This solution called “Instapaper” has also a killing feature!!! Let’s see together how it works and how it can help you.


First of all.

Instapaper is an application available on smartphones (IOS, Android), PC, and your internet browser.

Follow this link to access Instapaper:

What can you expect with Instapaper?

Instapaper provides a clear and simple interface to collect, store and read all the web pages you like.

My workflow

On a smartphone: When I see an interesting article, I send it to my Instapaper application. This article will be synchronized across the Instapaper servers and all my different machines.

On PC: When I have a question, I go to my favorite search engine and pick up 5 or more articles and send them to Instapaper.

Later (or not), I open it on Instapaper and start to read. It’s often on my smartphone when I have time. (In the public transport, sofa, waiting time, …)

5 features I like:

  1. Reader mode: Instapaper provide a better interface for you to read the article. Better format, font size, … A dark mode is also available, which is super cool!
  2. Highlight: I don’t use it after all, but I feel more concentrated when I Highlight important text and be happy to know that I can found it back if needed.
  3. Offline mode: Ok, now we always have an internet connection. We don’t also have a roaming fee in the EU. But it’s cool to be able to read your articles and disable your internet connection and be more focused. (Hey Instapaper dev team, if you read this post: A Pomodoro timer inside Instapaper could be a huge improvement!)
  4. Archive: I can archive the articles I liked (or I read) and find it back later. No more sorry when at the coffee corner we said. “I read an interesting article, I would like to share with you, but I don’t find it back”.
  5. Export a list of your links in an HTML format (easy to share with you colleagues or friends)

And I forgot to mention: THE KILLING FEATURE!! (At least for me)

Which is for me the best thing ever and the reason why I switch to the “Pro” / “Pay” version.

A nice Kindle integration!!

Instapaper allows me to send my unread articles to my Kindle. The configuration is pretty easy, and the result is very nice!

I receive the file through my kindle email address and can read all the internet articles with the beautiful E Ink screen.

On my kindle, all the articles are grouped in “one book” and each article is separated by chapter, which allows me to switch easily between articles. All Kindle features are available, you can highlight the text you want to save, search for a translation, or a Wikipedia explanation.

Reading with a kindle, I think there is no better choice to keep the focus on this task and it gives a different atmosphere to web articles.

I wanted to share with you because I simply think it’s super nice!!!

(BTW I’m not paid to promote their tool or the Amazon Kindle 🙂 )

If you like diversity you can also use:


Microsoft Edge Browser with the reading list.

In the last 6 years, I used Pocket but I quit when I saw the kindle feature on Instapaper.

Please comment if it changes your life too (or not), or if you have more tips to add!

LazyDAX V2: Learn DAX from examples

LazyDAX V2: Learn DAX from examples


Learn from examples.

LazyDAX helps you to understand DAX with concretes and simple examples. You can change the existing measures or create yours.
LazyDAX is also an easy dataset for your tests and presentations.

Why LazyDAX?


In my DAX journey, I met two kinds of peoples.

Business Analyst (sometimes also Excel Users) who had very good abilities to learn DAX.

And people like me, with a slow learning curve with DAX. (Unfortunately, I’m not so bad with SQL, C#, and a ton of different languages. Yes I’m a developer :))

During our DAX learning, Mathieu Ricour and I built the first version of Lazy DAX. It was a place for us to keep and save our code around a simple and concrete example.

After many months, I’m still using this file on a quasi daily basis. And I’m convinced, it can also help you.

In this second version, I’m sharing with you a list of useful measures and a reusable dataset.

Download it on GitHub


More measures and descriptions are coming soon.



Quick overview:


Power BI – Your model matters

Power BI – Your model matters

I’m trying to address a crucial topic (to me), but more complex to communicate than a technical feature.


This article gives you some tips and may give you the urge to look differently at your data. If so, my bet will be won, and you may significantly improve your Power BI trip.

Exciting, right? 🙂


Power BI is a fabulous tool that allows us to bring together the technical world of developers and end-users.

  • For a developer, it allows us to create beautiful visualizations and highlight the data easily.
  • For business users, it simplifies the technical work to focus mainly on the result.

Having worked at several clients, I am amazed by what users initially “non-technical” can achieve!


Users quickly become skilled in the tool, but sometimes lack a little methodology.

A habit, unfortunately quite common, is to multiply the models and then duplicate the data.

A question, a report corresponds to a data model. This is not always the case, but it’s quite often what I saw.

Several positive points to this:

  • Speed ​​of implementation
  • The size of the model reduced to the report need (Small size).
  • It covers the need.

But also, problems:

  • Duplicate data
  • Several different models and different logics/relations. Risk of having different results from one model to another.
  • Several models, more maintenance

As a BI developer, where the situation allows, I am a staunch defender of the unique model. With other Microsoft technologies, SSIS – SQL Server – SSAS Tabular / Multidim, we are trying to create what is called a Datawarehouse.

There are several methodologies for modeling this datawarehouse, but I will not dwell on it in this article.

A Datawarehouse is a data model that makes it easy to store, access, and understand your data.

Load Before, Think After

Two worlds existed and still exist.

BI (Developers / IT Service)

Let’s talk about me since that was the case. I juggled from one project to another by managing the business part as management of apple or pear. I did not bring much interest to the job or the nature of the data. Could I reproduce the reports asked? Yes! And I think everyone was happy like that.

Complex SQL queries, performance, calculations, rules implementation were my main concerns. I was the perfect example of developer 1.0.


Self BI (Users / Business)

The users I met have very different technical knowledge.

  • They have no particular interests or are panicked by the sources and structure of the data at their disposal.
  • They are obviously in a hurry to provide the reports fairly quickly

For all the reasons mentioned, when creating a new report, users are eager to load the data as is.

For both “worlds” the imperatives are:

  • Load the source data.
  • Provide a table or calculation as needed.

Methodologies – Quick Win

Without going into the details of the modeling of a Datawarehouse and, more precisely, the Kimball method, I want to dwell on two tips.

  • Denormalization

  • Brainstorming

The next two topics require the first change in your habits.

Do not keep the source tables as they are in your model

When you load your data into Power BI, you can make several changes in the Query Builder.

In addition to data typing, conditions, it is essential to consolidate the data.

This is the perfect introduction for Denormalization.


Normalization / Denormalization ?

In computer science, we tend to standardize information.

An example will be more concrete than a definition:

A product is available with a color.

A Color entity will be created and will contain all available colors.

In the source system, a drop-down list allow the user to pick up a color.

Often the main table retains a key (foreign key) that references the other table.

This way of exploding the model into multiple tables is called “normalization”.

For our reporting needs, we have to backtrack and consolidate information into fewer tables.

If we denormalize, our example could looks like this simple table.

  • Simple for your users
  • Simple for your model
  • Simple for your DAX measures


Concrete example

In this example, Bill tooks all the tables and files from his source system. He decided to load the table as is, without any changes.

It was easy for him and he knows very well his model. But his users came back to him with a ton of question regarding interactions. Which tables will be impacted if they filter one specific attribute. They were not really sure.

Since they have the “Sales Person” in their model, they wanted to know if Gender or Marital Status were link to “Sales Person” or “Client”. (So bill, renamed it to make it clear)

One day Bill wakes up with a giant smile! Is it because his favorite TV show is scheduled today? Not only! He has an idea… And a straightforward one.
He decided to group his data into fewer tables. (When there is no many to many relationships).
His work life changes to better!

  • Less complex DAX expression
  • More understandable datasets
  • Less support and more time to watch his TV show. (Yes, both are compatible!)


The title should perhaps have been: Do not keep the focus on the technical problems but think of yourself.

We all tend to want technical challenges, it’s addictive, and it gives us the impression of moving forward! In our Professional world, Power BI is the equivalent of Candy Crush! But I have more pleasure in aligning beautiful DAX measures in a table than sweets, do not you? For this point, I invite you to step back and step against our technical world.


Ask yourself the following questions: (or ask them to your users)

My advice: Take a pen, paper, coffee, soft music. Disconnect from your computers, technical “worries”. Make sure your explanations can be understood by your wife, your husband, your friends, your sports coach, your children … and yourself …

  • What is the nature of your work? Describe it to me.
  • What are you doing within the company?
  • What indicators and reports do you consult?

Take note of the information in the form of keywords and mention the frequency. Some words will stand out and can be likened to what we will call later “Dimensions”.

    Your notes could look like this word cloud.

    See if some words do not relate to each other through an idea or logic.

    For example, [Customer Code] and [Customer Name] could be grouped under the same “Customer” dimension. (While these are potentially in two different tables or source files)

    The watchword here is: DO NOT THINK TO THE TECHNICAL ASPECTS. Without knowing it, you imagine the data model dreamed for you and your users. It fits your needs, your business, and does not care (yet) about the complexity needed for the data transformation!

    In this model, an end-user will find it much more comfortable and can even build their reports. Attributes will be displayed, grouped by logical ideas, and will facilitate reporting.

    The attractiveness of Power BI and BI Self-Service, in general, will not only be available to you, but it will also be accessible to end-users.

    Now that you’ve sketched out your dimensions, you can link them together.

    You certainly have information that expresses an event with measurable data. (Additive data)

    For example:

    • A sale with a price, a quantity.
    • An inscription with a volume, a frequency.

    The relationships mentioned above correspond to Facts.

    A fact table is defined by its grain, which is itself determined by the list of dimensions attached to it.

    The sale is made:

    • By a customer
    • For a product
    • In a store
    • On a given date
    • With a means of payment

    The inscription bears:

    • On a magazine
    • By a subscriber
    • For delivery to a specific address
    • With a subscription end date

    A brainstorming session can quickly give you a good overview of your next dataset.

    Your fact table is in the middle and dimensions around.

    Where is the technical complexity for your users? For your DAX measures? Your users can now keep the focus on their results and to the more complicated question: Do I really avoid to use a Pie Chart 😉

    You can now look in detail how you will load your dimensions. Dimension by dimension asks you the question: Which is the grain of my dimension? Household, client, client history?

    And now start your candy crush session, load your data, and play a lot in the query Builder / SQL / … more …
    And do not forget to enjoy it, our work is exciting!

    How to put all this into music

    Power BI gives you the ability to consolidate your data into the Query Builder. (Power Query for the intimate)

    Do not minimize the time spent in this step, it will save you a lot later.

    You will be able:

    • Group your data (multiple source tables can be grouped) into a single table.
    • Clean up your data. (Filter unnecessary data, edit poorly formatted data) This step will provide more convenience to your users.
    • Add a type to your data.

    The interface is quite complete and allows you to perform all the desired fantasies. For performance reasons or more flexibility, you can achieve your work on data with SQL queries.

    I do not have doubts about your technical abilities to perform this task.

    The final word

    Take a step back on your technical problems, and nothing stops you! Take the time to rediscover your craft with an outside look! Power BI offers you the technical means to achieve this. And with a little methodology, you’re entering the big family of Datawarehouse’s happy modelers.

    Give me your feedback or your comments.

    I would be thrilled.



    P.S. This article is a part of my session Power BI and Data modeling – Go to the Stars!

    Read more:



    PIT Point In Time

    PIT Point In Time


    We often have descriptive data in our Power BI models. Data may vary over time and have validity dates. It can become a real headache when creating a data model.

    What kind of data?

    • A car could change his production plant through time.
    • A car can have different engines over time
    • A customer can have through time:
      • One or more loyalty cards
      • One or more addresses

    What data types?

    • Multiple data
    • With a notion of time. (The information is valid from one date to another and potentially followed or overlapped by another)

    PIT – Point In Time – Datavault

    Point In Time is a concept widely used when creating a data warehouse in a Datavault flavor. Performing a snapshot and historizing the data makes restitution much easier.

    (I will not discuss the pros or cons of Datavault, but I have my preferences ^^)

    If you want to know more, I invite you to read this article. (Written by Dan Linstedt)


    What do we expect?

    It is exciting for our users to navigate through the data by applying a time filter (CFR Slicer Date)

    How: By creating a DAX measure. (#PIT Shoes)

    The example above shows dynamically Pauline’s shoes.


    Our data model

    The following example is quite simple (The Power BI file is available for download at the end of this article)

    Many of you know it, I am passionate about Power BI, running, but many ignore my “passion” with running shoes. (Nobody is perfect !)

    The example refers to a list of runners who have one or more pairs of shoes over time.

    The Runners table:

    The Shoes table

    Model specificities

    • RunnerId (The Runner Table Key) is available for all shoes.
    • For performance reasons, the date stamps are duplicated and converted into numeric.
      • ValidFrom – ValidFromInt
      • ValidTo – ValidToInt

    More information

    This is denormalization of a star schema generally composed of a Bridge and a dimension table.

    In a Datawarehouse (Kimball), we should have a Bridge: BridgeRunnerShoes and a dimension: DimShoes


    It helps our users to have better comprehension. (Simplicity)
    The Vertipaq engine will compress the redundant information
    To avoids an extra join / relationship.

    You want to know more about Bridges:


    A more complete model could look like this one


    Graphically analyze the different interactions.

    1. Our user pick a date via the PIT Date slicer
    2. The shoe table changes dynamically and display the one owned on that date.

    NB The blue bar drawn on the timeline has been added manually in MS Paint. (If you know a visual component that can display it, do not hesitate to contact me)

    Filter: 01/02/2019 | Pauline

    Filter: 01/03/2019 | Pauline

    Filter: 01/05/2019 | Pauline

    Filter: 10/10/2019 | Pauline

    Filter: 01/12/2019 | Pauline


    Create a Calendar table

    We have to create a Date table, which will not be associated with our model. (Called here PIT Calendar)

    To quickly create a Calendar table, I suggest you write an M Query in the Query Builder. The following articles will give you the approach.

    Generating A Date Dimension Table In Power Query

    Create a DAX Measure

    This measure Filter the Shoes table by the selected date.

    #PIT Shoes =
    VAR CurrentDateInt = MAX(PIT_Calendar[DateInt])
    Shoes[ValidFromInt] <= CurrentDateInt && Shoes[ValidToInt] >= CurrentDateInt
    ; ‘Runners’

    Understand this DAX expression

    VAR CurrentDateInt = MAX(PIT_Calendar[DateInt])

    VAR CurrentDateInt =
    ;VALUE(YEAR(TODAY())*10000 + MONTH(TODAY())*100 + DAY(TODAY()))

    A variant of the previous expression can test if our user specified a PIT Calendar date and apply the current date if not.


    • The user wants to have the situation of the day (without having to modify the PIT slicer at each opening of the report)
    • The user forgot to create his report with the PIT slicer. Rather than propose the situation in the future, we apply the current one.
    Shoes[ValidFromInt] <= CurrentDateInt && Shoes[ValidToInt] >= CurrentDateInt
    The variable contains the date selected by the user and is dynamically applied to our dataset. (Shoes)


    Now, you know how to make your data alive.

    Feel free to comment if you have more ideas, improvements, tips, or comments.

    Download the Power BI example file here:


    Management Studio – Faster with multiple select

    Management Studio – Faster with multiple select

    In SQL Server Management Studio (SSMS for close friends) but also in a multitude of text editors (such as Notepad++ for example), you can make multiple selections.

    I thought it was something everyone knew, but I realize that I often look like a magician every time I do it.

    I’m delighted to pretend to be Harry Potter, but I think it’s time for this little game to stop!

    Look by yourself how simple it is!


    You should press the keys [ALT] + [Shift] simultaneously and move your cursor [Up] and / or [Down] to select your text.

    One useful case

    Sometimes we have to surround our text with single quotes. (for example: to add multiple codes to an IN clause in a test query)

    No need to add them one by one and make sure you do not have space at the end.
    Here is the method:

    Like mentioned above, this tip is not an exclusivity in SSMS, you can also do the same in many different text editor.

    Pin It on Pinterest