Sign in

Web Developer @ Atos | UI/UX Senior Expert | Passionate about martial arts | Shotokan karate black belt and BJJ blue belt | CSS is my dojo

Recently I came across some bugs in an app I developed that only affected iPhone users.

When encountering a bug, the first step is usually to try to reproduce the issue and then to analyze it with developer tools. iOS however, is the most difficult environment to debug/analyze unless you’re fully committed to Apple and are the proud owner of both an iPhone and a Mac. If you are missing any of those, you get no developer tools to debug. But let’s get back to that a bit later.

The development environment

Developing on fast machines with (multiple) big screens and fast (wired) network is always pretty convenient and what most developer probably prefer when giving the choice.


Code coverage history graph in Gitlab

One might think that this should be pretty straight forward and shouldn’t require an article, at least I did. But when I tried to set it up for some of my projects, it took me much more time than I expected.

There are some hoops you need to jump in order to get it to work. Each of which can be found somewhere on the internet, but getting them all together happened to be somewhat cumbersome. So I decided to write a quick how-to and get all the tricks together on a single page.

The first pitfall

Since you’re probably already running unit…

Working with SCSS and LESS, I’ve become used to see people using mixins and I used quite a bunch of them myself. Over time I’ve seen them being used in several different ways, some of which I think aren’t good.

But let’s start with…

The good 😊

Mixins allow you to have a single definition for a group of properties that are used throughout your code with different values by simply replacing the mentioned values through variable parameters.

Thanks to this you don’t have to repeat the same code over and over again or don’t have to create multiple classes for each potential…

When you start working on a new website or a web app, chances are that you don’t spend much time thinking about code style or code quality. Why?! Just because you already have a well configured IDE and you reuse the same coding guidelines that you already know by heart over and over again.

Everything changes when you start collaborating with other people. Suddenly you start looking at code that looks nothing like yours. It gets even worse where multiple styles start mixing in the same file.

There are many reasons for this situation… They might use different editors, follow…

Michaël Vanderheyden

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