Another Thursday. Another Code Jam review because writing about anything else would have taken even more time…
Back in 2015, Google open-sourced its internal build system, Blaze, under the anagram name of Bazel. Since then I had worked to migrate and unify the various build scripts in my company into a single Bazel workspace.
Not long after, however, I decided that maintaining a Bazel workspace is not the best use of my time. I worked on other projects, and created an unrelated open source Bazel workspace for my own enjoyment.
This post will be a brief introduction of this project.
This Round 1A was crazy. I was barely awake when it started, and I spent about two hours on the first problem — which is probably going to be the hardest problem one in historical first rounds!
Anyway, it turned out to be OK for me as the other problems were easy and I was good enough to enter the next round.
tl;dr: I will try to write something every Thursday from now on.
It was probably depressing to realize that I have not participated in any programming competitions since the last October. It is more depressing that I nearly missed the Code Jam of this year: I received no notification mails and I did not think of it either. Anyway, I was lucky that someone informed me that it has begun in the last few hours, and here I come.
Since I have just updated to WordPress 5, it seems appropriate to start investigate what changes do I need to keep in mind if I am to switch to Gutenberg.
While I have been using WordPress 5 on my local test server for months, I still worried about possible breakage caused by an update. Anyway, if my Gentoo experiment is any indictment, then I should have come to the conclusion that “not updating your system” breaks the system worse than “often updating”. The point is that by holding off updates for a long time, there has to be a point where new software start to be not compatible to your base system, and reverting to old versions gets harder and harder. And if you only fix it then it finally breaks, it might has already become a mess that’s impossible to deal with.
Hence, despite the concerns, here I updates the website.
Yesterday I received an email from Let’s Encrypt, the certificate provider I have been using and previously talked about in a previous post.
The mail says:
Your Let’s Encrypt client used ACME TLS-SNI-01 domain validation to issue a certificate in the past 60 days. Below is a list of names and IP addresses validated (max of one per account):
ahyangyi.org (188.8.131.52) on 2019-01-16
TLS-SNI-01 validation is reaching end-of-life. It will stop working temporarily on February 13th, 2019, and permanently on March 13th, 2019. Any certificates issued before then will continue to work for 90 days after their issuance date.
Seems a quite urgent issue, since it will actually break my setup if I do not take actions. Admittedly, this blog has been in a hiatus lately, but I do not want to see it dead.
Two months have passed since the last time I wrote anything on this blog.
What has happened?
I have not written anything on this blog for about four weeks. There are various reasons, including procrastination.
Part of the procrastination process caused me to join a play-by-post Dungeons & Dragons 4E game on GitP forum. Anyway, since the time is already wasted, why not waste it well? So let me document the stories of the games I am playing.