CSS has a maintenance problem and preprocessors or current CSS architectures don’t help solving it. Instead they reinforce the language’s weaknesses and add more problems. But we can use components to do better.

I’ve already written about how to write maintainable CSS, but since this is still quite controversial for many I’d like to elaborate my point from a different perspective.

How do you decide which tool to learn next or which one is better? Learn about generic and specific knowledge as an important criteria when evaluating software.

This post contains the solutions to exercises which could be found on Elm’s official page for version 0.15.

I’ve never met someone who loved working with emails. If “Inbox Zero” is a term there certainly has to be a design problem. Recently I’ve realized why there is so much frustration when we have to deal with our inbox.

Because Elm is based on functional reactive programming concepts, dealing with time is different to most other programming languages.

While learning Elm I missed a tutorial that shows how to build an app from the ground up, which does an HTTP request and uses the StartApp package. This is why I wrote it myself.

When writing JavaScript I am used to have a tool like Webpack or Browserify that automatically compiles the code whenever I save my changes. Therefore one of the first things I wanted to do in Elm is to set up the same workflow.