Nearly every technology that has been developed has been used for both good and bad. Developments that look like they could have a massive impact on civilization have usually also spun off a side effect that has a detrimental effect. This could be the latest technologies such as genetic engineering and artificial intelligence or older technologies such as the automobile.

I read a lot of books and once I start reading a book I normally finish it. This article proposes that it may be more valuable to have a bunch of books that are unread. Not sure I completely buy in to the proposition that "Read books are far less valuable than unread ones" however maybe I won't feel so guilty buying a book and then leaving it unread.

Just a reminder of the starting point for setting up SSH with Github so I don't have to keep looking for it each time.

This has a great summary of what to do when things go wrong when using Git. Added here so I know where to look in moments of panic.

The background to why the famous "three finger salute" was chosen to be so difficult to do.

I am back on the learning Scala trail and it is clear that just reading books and articles or watching videos won't cut it. It needs to be hands-on coding.

I am currently starting to learn Scala (to add to a myriad of other languages I have programmed in over my career). We are also in the process of "dockerizing" our application. So I wanted to try for myself getting a simple Scala application running in Docker.

I have never been a fan of performance reviews. It may have been down to the way they were implemented at the places I worked however they never seemed to achieve what they were set out to do. The review would usually consist of going over the "achievements" for the past period and then setting a bunch of artificial goals for the next period. The only time these new goals were actually consulted was in the run up to the next review.