Image for post
Image for post
Photo by Will van Wingerden on Unsplash

I want to inform you that my future articles will be published on and

I’ve been writing blog posts consistently for almost 2 years now, and most of my blog posts are published here, on Medium.

Until a couple of months ago I was happy with the platform, it even allowed me to get in touch with the AngularInDepth publication and its great writers.

With this last post on Medium, I want to thank you for reading my articles.
I also want to invite you to my personal blog at, and to the InDepth platform.

To keep being notified of my future articles, give me a follow on Twitter and subscribe to my Newsletter.

Thanks again, and see you soon!

Image for post
Image for post
Photo by Andrew Neel on Unsplash

At first when I heard of css variables when it was introduced, I was a bit skeptical. Why would anyone use it if there are extension languages as scss, sass, less and stylus. After several years, I started to notice more and more peoples using it, writing about it and talking about it. I was missing out on something… It took a while but after using it here and there, I was hooked. In this post I’ll cover what convinced me to explore css variables further and to start using them in projects.


To declare variables, define them in a…

Image for post
Image for post

Today we’re happy to announce the version 8 release of the NgRx platform. This release contains a lot of new features across most of the libraries, bug fixes, and some breaking changes, all aimed at improving the developer experience when using NgRx libraries.


The long-awaited angular-ngrx-data library by John Papa and Ward Bell has been integrated into the platform as a first-party package. NgRx Data is an extension that offers a gentle introduction to NgRx by simplifying the management of entity data while reducing the amount of explicitness.

For more info head over to the docs.


createAction, actions without enums, classes and union types

In previous versions of…

Image for post
Image for post
Photo by Tim on Unsplash

This post is not a post that says you have to have between X and Y percentage coverage throughout your code base. It’s an introduction post to code coverage, how to read it, and how you can use it in your workflow.

Code coverage

Code coverage tells you which code has been executed during a test and how many times. I’m not telling to aim for X percentage of coverage, because this is entirely dependent on what you’re creating. Targeting for 100% code coverage is often a mistake as it will take a lot of time (to get there and to maintain)…

Tim Deschryver

NgRx team member — Writer for AngularInDepth —

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store