Having played three games in Food Chain Magnate, I would announce that it is my new favorite board game, or, at least one of them.
Yeah. The first season is finished. The nature of amateur football dictates that even if I control the manager, I have absolutely no power to prevent other teams from signing my players. The total monthly expenditure of the whole club is nearly zero, since everyone essentially works for free — or “for the love of football”. After all, “Amateur” used to mean “lover”.
Last week I created a post and a page.
The post was this. I wrote about what my first game setup was like, and what difficulties I met with trying to run the game under Linux with Steam Play.
The page, available here, was on the other hand not supposed to be a publicly viewable page. At least not until I have added in more stuff. It contained various technical details of what I did to get my first game running, so that I could follow it step by step and continue my game on a second PC.
Naturally, both the post and the page were named “Football Manager 2019”. Guess what? The generated permalinks are also the same. For both the post and the page they are https://blog.ahyangyi.org/football-manager-2019. The page took priority over the post. Hence, even if the main page shows the correct digest of the post, clicking “read more” would show the content of the page instead. And it was a page that was supposed to be secret at that point…
There were, many different naming schemes that I could use. Unfortunately, I have already made the decision back in a time I did not know about any potential issue, and now it is perhaps a bit too late to change it, as I have used many internal links, this very post also adding to the injury.
What I did not expect is that there is no mechanism of conflict detection whatsoever.
It seems that, given all these considerations, I have to be careful with names.
As Football Manager 2019 was on sale I bought it. To my disappointment, however, it was the first version that does not support Linux in the recent years.
Anyway, complaints be complaints, I will start my first game.
Last year I managed to find a group to play Dominion semi-regularly. It prompted me to buy yet another expansion. I picked Nocturne for its lack of extra components. It was probably a mistake, since Adventures, Empires and Renaissance all provide more variation to the game, while Nocturne adds more complexity.
Anyway, back to the topic. It began to feel clumsy to move the four boxes around. It is time to find a storage solution.
I seem more motivated to write about my failures. I sucked at round 3, and I immediately started writing this post.
As I started writing those Google Code Jam posts, I grew unsatisfied with the blockquote option offered by the current theme: walls of text was set in big, italic typefaces. Not the most readable choice.
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.