Wejście w życie RODO/GDPR napawa mnie wielką radością. Już masowo nakazałem usunięcie moich danych osobowych firmom, o których już dawno zapomniałem, albo o których nawet nie wiedziałem, że mają ze mną cokolwiek wspólnego.
To też okazja, by trochę się pośmiać i ponarzekać:
Meinen Rechner hab ich von mySN.de / Schenker Technologies gekauft. Es scheinte eine gute Idee zu sein. Was es aber gar nicht. Ich fühle micht von mySN betrogen und we Müll behandelt. Ihre Kundenservice ist voll unprofessionel, ihre Hardware ist Scheiße und sie scheinen sogar nicht zu wissen, was sie im Lager haben und wie viel ihre Teile kosten. Im Ernsts!
Das ist mein (verkürztes) Geschichte:
I’ve bought my laptop from mySN.de / Schenker Technologies. It seemed like a good idea at the time. But it definitely was not. I feel scammed by them, I feel treated like trash by them. Their customer service is unprofessional, their hardware is crap and they don’t even seem to know what they have in storage and how much do their parts cost. Seriously!
Here’s my story in short:
jQuery used to be virtually indispensable, if you wanted to develop a cross-browser website without getting a headache.
Today, however, you might not need jQuery, especially, if you’re developing a library and want to avoid unnecessary dependencies.
Still, some helpers could be useful... Vanillin is an opinionated set of helpers that I find most useful, a bare minimum to make life easier.
Keeping your classes immutable and stateless makes your code way less prone to bugs. Yet somehow this clean code rule isn’t as popular and as often invoked as SRP, YAGNI, DRY, KISS and others... Maybe it’s because of the lack of a catchy acronym?
Anyways, I’d like to take a look at two examples of when sticking to this rule could save your ass (or at least save you some time debugging).
If you can’t decide to improve yourself in the middle of October or April – don’t kid yourself, starting on the 1st of January won’t magically help you with that. Start whenever you’re ready, start because you want to self-improve, not because you have to 😉
Having 100% of LOC covered by unit tests certainly feels like a great achievement. But beware – that doesn’t necessarily mean your code is perfectly covered. Lines of code coverage is a really nice indicator of your app’s stability, but is can also hide some risks.
A musical competition, in which the managers lead their countries every week to a fight for a title of the best song.
I’ve been taking actual HIV drugs for a month.
It doesn’t feel like something you should admit to publicly, does it? And that’s exactly why I decided to write about it. The stigma around HIV is so huge and baseless, I’m hoping to reduce it, even just a tiny bit. And hopefully to make some people aware that something like PEP even exists.