It’s honestly diffucult being a webdeveloper in the world of shitty websites. I guess that’s how hairdressers feel when they see my pathetic hair after it’s been a while since my last visit...
But the thing is, even though it’s technically easy to use scissors and clippers, I don’t do that on my own hair, I leave that to the professionals.
I had to learn Git as a programmer. If you want to easily collaborate on a codebase, you really need either Git or something similar. But as a non-programmer, you’ve probably never even heard that name, have you? Then why would you ever need it?
Well, for exactly the same reasons!
Ofkors, trik działa też dla mentions.— Avris 🇪🇺 🏳️🌈 (@AvrisIT) 31 mei 2018
Zaprezentuję na przykładzie @WojtekWernickiego 😁
The story I described in here finally has a bittersweet ending – I finally got my computer back! After over two months, after lots of stress and fighting, and after having paid them 130€ (only 25% of what they first requested, but still 100% more than I should have paid)...
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:
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).
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.
Programming isn’t that hard. Really. With enough time and determination, almost everybody could write some useful code. The Internet is full of tutorials that teach you programming from scratch, full of people who faced the same problems you do, full of people who solved those problems and shared their solutions for you to use, and finally full of free libraries that you can just use. All you need to do is learn some tools, google your problems and put together pieces of code that you find.
But if it’s not a black magic, not a secret knowledge, then why are software developers so well paid?
When I first heard the term “Autowiring”, I thought it sounds exciting. But when I learned more or less what is it about, I got pretty sceptical of the idea. Too much magic, too much implied information... However, when I finally used it for the first time... Gosh I wish I could never define services manually again!
To those living in technologically advanced countries it might sound strange. But yes, here in Germany people do have a noticeable fear of PayPass.
I moved here two years ago and during that time I’ve witnessed a huge revolution in the field of payment methods. A revolution that is still way behind where Poland (Poland!) was already five years ago!
Putting emojis in your database should be a piece of cake, right? You’ve had enough trouble with encodings in your lifetime, and now that we have the blessing of UTF-8, you’re always so careful to use it everywhere, so you’d expect all the characters to just finally work out of the box, right?
Well, I did expect that. But I’ve recently realised I can only put some emojis (like “❤️”) in by blog posts. Most of them were just lost or replaced with “?” by MySQL... Oh, those damn encodings again!
But fortunately the solution is quite simple.