Good question!

While finishing my bachelors degree and starting the second one, I started more and more to learn stuff related to web development that I found useful for me.

Most of this wasn't taught during my studies at the university. So I had to get things up working by my own.

Running through a lot of tutorials and plenty documentations (which can be - let's say - demanding in terms of getting what they're really trying to say), at some point I always had the issue that something didn't work as I suspected it would. Not seldom also because I didn't read the documentation to the very end or thought I won't need that specific chapter and just skipped it. Well, bad for me. Once the frustration level reached my treshold, I quit and would start again a few days later.

But after getting familiar to web development and getting the concepts behind things, it got easier and was quite fun. Fascinated by the concepts of the web and how everything was working together, I wanted to learn everything at once. I didn't finish what I started while already heading over to the next thing. The result: Everything "In Progress" and nothing "Done".

But every task had one thing in common: Questions about how to do it the best way and how to solve specific issues down the road.

This blog mainly focuses on showing tips and tricks for all kinds of stuff that might be interesting for a (web) developer. The main aspects might (but won't be limited to):

• Frontend frameworks, like Vue.js and React.js or "On-Top-Frameworks" like Nuxt.js

• Docker

• Setting up servers with e.g. Ansible

• Backend frameworks, like NodeJS or Spring Boot including libraries like ExpressJS

• Programming languages like Javascript/ Typescript, Go or Java