Subscribe via RSS

Schon wieder gehackt

Fast genau vor einem Jahr war ich ziemlich in Panik als klar wurde, dass mein EA/Origin Account gehackt und scheinbar verkauft wurde. Nach einigen gescheiterten Versuchen das Problem über die digitalen Tools selbst zu lösen, konnte mich der Telefon Support zum Glück retten.
Das war dann auch der Zeitpunkt an dem ich endlich bei allen Services, die es anbieten, 2 Factor Authentication aktiviert habe. Hätte ich mich da schon früher drum gekümmert, wäre das nämlich alles nicht passiert.

Wie komme ich da jetzt drauf? Heute morgen wurde ich an diesen Erlebnis erinnert, weil ich eine Mail von Ubisoft bekam, die eine Ihnen suspekt vorkommende Aktivität in meinem Account festgestellt haben. Es wurde sich nämlich von Polen aus in meinen Account eingeloggt. Ich hatte natürlich keine 2 Factor Authentication aktiviert und wurde tatsächlich mal wieder gehackt — selbst Schuld könnte man sagen. Ich habe die Mail glücklicherweise sehr früh gesehen, konnte mich noch einloggen, das Passwort ändern und die 2FA aktivieren. Also diesmal alles gut gegangen, auch ganz ohne Telefonsupport.

Ich kann euch wirklich nur sehr empfehlen überall wo es möglich ist die 2 Factor Authentication zu aktivieren. Apple, Google, Dropbox, EA/Origin, Steam, usw.

How to sync iCloud calendar with Windows 10

Today I wanted to add my iCloud calendar to the Windows 10 calendar app and everything I tried failed until I remembered that I use two factor authentication and that I might need an app password (like with so many other services like Google or FastMail) instead of my normal Apple password - even though the calendar app never said that my credentials were wrong.

So I looked on to generate an app password. Nothing there. Turns out, to create an app password you need to go to and locate the Security section there to “Generate Password”. Then you can use that password in the Windows 10 calendar app and everything should be working. 👍

Photos from Rügen

The sea with a boat
Dark Pine Forest
A trail next to the sea
Coast with trees
The sea with two big rocks in the foreground
A trail in the forest with a tree in the foreground
Looking down on a wooden flight of stairs
Looking through the trees onto the sea
A stump with a sign on it pointing to the left
A generic view in the middle of the forest
Looking at the green covered ground of the forest with trees in the background
Looking at the treetops
A very big and old tree without foliage
A very small, young tree
A view of a trail with a small railing and the sea in the background

Italic Comments in VS CODE

In a recent post I explained how to get programming ligratures for the font Operator Mono. Operator Mono also has a very special italic font style which is often and gladly used for comments in code editors.
You can get those fancy italic comments in VS CODE by adding this to your user settings:

"editor.tokenColorCustomizations": {
	"textMateRules": [{
			"scope": "comment",
			"settings": {
					"fontStyle": "italic"

Add ligatures to Operator Mono

Operator Mono (ScreenSmart) by Hoefler & Co is a beautiful font which I love so much that I paid a bunch of money for it a while back because it makes writing code even more enjoyable. But sadly it lacks programming ligatures like the ones you find in Fira Code for example.

Luckily someone took it upon themselves to create these ligatures for Operator Mono and wrote a script to create duplicates of the font files with these symbols in it.
Assuming you bought Operator Mono and thus have the original font files you can clone the operator-mono-lig repository and create your own “Operator Mono Lig” version. I tried it out and it worked perfectly. 🎉

You can find all the information on how to do it in detail on GitHub.

Some photos from a sunday morning walk

Three drinks - one red, one yellow, one dark brown - in plastic cups.
A jam-packed trash can under a tree with cherry blossoms.
A close up of cherry blossoms.
Very smooth waves of water.

How and why to use a Github branch as a dependency in your package.json

The combination of Open Source and GitHub is amazing. I can not count the times a freely accessible library or tool saved me countless hours or allowed me to built something I wasn’t otherwise capable of.

But sometimes you might not be happy with how a library/framework/tool/whatever handles something and you need a little change. Oftentimes for me that requirement is so specific to my project or problem that creating an issue makes no sense. Or maybe there is just no time to wait on a response and update.

Luckily you can fork a GitHub repository, change or fix it yourself and then pull the repo into your project right from there instead of pulling the npm package in. You can even point to a specific branch.

You can do this by either running the npm or yarn command on the CLI or by going the manual way editing the package.json

Command line

npm install --save-dev username/repo#branch-name
yarn add --dev username/repo#branch-name

Manual way

Open package.json, to to the "devDependencies" or "dependencies" key and add your package in the following format:

"package-name": "username/repo#branch-name",

And then install the package with npm install or yarn.

Don’t forget

If you already had the original version of the package in your project, make sure to remove it (and install your new package).

rm -rf ./node_modules/package-name && npm install
rm -rf ./node_modules/package-name && yarn

Or find the folder inside node_modules you want to replace and remove it and then npm install or yarn again.

If the change/update might be of interest for others too you can also create a Pull Request to the original package and see if your changes make it into the Repository and then you can maybe switch back to the original later.

This has the advantage that you will get further updates - which you won’t get in your own forked version. But Depending on your changes or needs that might also be a good thing. As always: It depends.


Blossom in backlighting

Original RAW, cropped to 2x3

Blossom in backlighting

Edited with VSCO

Coffee at The Visit Berlin

Sign reading

About a month ago Pascal was in Berlin and he showed me The Visit Berlin. The place is cool and the coffee delicious. If you get the chance, stop by.

A cup of coffee
Pascal looking at his iPhone

Pascal looking at his iPhone

A Restart

First, a little backstory. 😴

This website was once called, a blog about all things web development. But after a while I decided to turn it more into my portfolio website with blog attached and switched the domain to to I also had - or rather have - another blog, which is more or less only a photo blog by now (

I’ve been running both blogs side by side for a while and then realized one or the other is always suffering, so I closed the Blog and made this website just a simple portfolio site. I stopped writing about code and also only rarely posted photos to the other blog all while posting less and less to social media sites like Twitter or Instagram because it just doesn’t feel as good as it used to and I still get more and more concerned about what happens with my data.
Which brings us to today.

I like personal blogs and I like RSS. So I want to get back to that more. I also like code as well as photography. And I still like to publish personal journal-type things. So this website here shall be my new home where I hope and plan to post more regulary - also shorter status like posts. My life, code and photography will probably be the main topics, but basically it’ll be just what interests me. So be prepared for some gaming content as well. For now I’ll be posting in English 🇬🇧, but we will see if I can keep that up.

I’d be happy if you come along for the ride. Thank you for reading! ✌️

PS: Make sure to subscribe to the RSS feed if you want to follow along. Ah, and this site might be still a little bit rough around the edges or content might be missing. It’s as work in progress. 🔨