I was moving few of the sites I manage to HTTPS lately. I’ve messed up on one of the sites and I had to revert back to plain HTTP. Ok, so I revert hosting configuration, enter url into Chrome address bar and…. Chrome shows errors and I see my site address over https. Refresh, same thing. Hard refresh, still same. Remove “s” from “https” in the address bar, still same situation.
Recently I haven’t written any thoughts about books that I read. Time to get back to this. It’s kind of funny how my book choices changed over the years. From very specific positions, treating about C#, ASP MVC, RabbitMQ etc. I moved my focus towards the universal knowledge. So I was reading ‘Clean Code’, Gang of Four Design Patterns, books about algorithms and so on. As I still like to read those technical book, I enjoy another set of titles on my bookshelf: self and business development related.
I’m a ‘console guy’. I usually prefer any type of console/text based interface over sweet and colorful UI. Same applies to my favorite source control - GIT. But there is nothing that prevents us to get fancy in our terminals. Meet diff-so-fancy. GIT is great for handling your code, showing repository log in any way you want, but when it comes to showing a diff, we’re basicly stuck with the standard patch format.
Handling errors is not something new, it was always part of good practices. But from simple, monolithic applications where in huge number of cases we could think of scenario that will throw exception, we are now moving to complex architectures, with many independent components talking with each other over the network. That means, we need to cover for a lot more situations related to intermittent issues (it could be temporary network failure or just some component being down or upgraded).