I was following the GraphQL story already quiet a long time. And I finally decided on a very good project to try building a GraphQL server. In this article I am going to use the Hyperwallet REST V3 APIs and expose them via a GraphQL Server.
I recently applied for a online freelance platform and as part of there interview process I had to take a mandatory algorithm programming test. In this article I am gonna explain why I think that a test like that is very useless to evaluate the quality of a programmer.
I recently came across the blog post Universal React: You’re doing it wrong by James K Nelson. His main statement in this article is, that universal react applications are not necessary and you should avoid using the history API and developing a universal application to safe time.
I think everyone has heard about the current NPM-gate by now. But there are easy measures especially for companies to prevent problems like that for their internal development. This is not going to be just another review of the issue and trying to figure out who is right and who is wrong. Instead I am going to explain ways to prevent issues like that from happening and blame our self (including me) for the issue.
If you’re android application is consuming a web-service you most likely use https for the secure communication with your API. Looking at the news recently we see more and more openssl issues getting found.
I recently had to work on an Android application that consumed an API which removed support for TLS 1.0 connections for security reasons.
The Android documentation for SSLSocket says that TLS 1.1 and TLS 1.2 is supported within android starting API level 16+ (Android 4.1, Jelly Bean). But it is by default disabled but starting with API level 20+ (Android 4.4 for watch, Kitkat Watch and Android 5.0 for phone, Lollipop) they are enabled. But it is very hard to find any documentation about how to enable it for phones running 4.1 for example.