It doesn’t always have to be a todo list

As developers we try out a lot of things. New libraries and frameworks, the latest language features and so on. What’s the best way to do so? Yes, you’re right: write a simple application that has as many different features as possible to cover as many aspects as possible. So imagine you’re new to, let’s say Angular. What are you building first (of course after the awesome heroes application)? A todo list. Then you maybe want to try out React. What are you building? Another todo list. And so on. After a few frameworks it’s getting more and more boring – it’s time to think of alternatives.
Continue reading “It doesn’t always have to be a todo list”


What is so special about Yarn? Basically Yarn is just another package manager for the web – like NPM or Bower. But it has some features that make it worth to have a look at it. If you go to, the website of Yarn, you get a list of key features of this package manager:

  • fast
  • secure
  • reliable

That pretty much sums up what the creators of Yarn learned from the mistakes of the other package managers. Under the hood, Yarn is not a revolution of package management but the next step of evolution. Continue reading “Yarn”

A quick look at async/await

If you’re working with JavaScript, you have to deal with asynchronous operations. Long time ago we did this by using callback functions. Nowadays we’re using promises to make our code more readable. Additionally we get a pretty good tool to handle asynchronous program flow with promises. If your application is a bit more complex and there are multiple asynchronous workflows in your application, your code is likely to get messy over time. You will implement multiple callback functions to handle success and error cases and stack them all together to build your application. To make your life easier ECMAScript defines a new feature called async functions.

Continue reading “A quick look at async/await”

Node.js Debugging

A while ago there was an article on how developers use Node.js by Rising Stack. In a survey they asked Node.js developers for example what kind of database or message queue they use. Beside the question on how users deal with async programming one of the most interesting topics was debugging. Over 80% of the participants use console.log in order to debug their application. This made me think. Often I find myself inserting console.log statements in my code in order to see what’s happening – but why? The answer is easy: It’s inconvenient to use the debugger if you haven’t set up your environment correctly. In this article I’ll show you different approaches to debug your applications and their advantages. Continue reading “Node.js Debugging”